fix(nodejs): register import in the middle for nodejs24.x runtime

[wpessers]

solves #2034

This change has been tested and fixes aws-lambda instrumentation again for commonjs lambda handlers using node 24 runtime.

[wpessers]

@serkan-ozal @pragmaticivan any thoughts about this? Also tried quickly to add a handler test like the ones we already have. But is difficult to add something "lightweight" since import-in-the-middle is loaded already in other test and you can not really "unload" it. So not so easy to isolate from the others.

If wanted, I can setup a simple unit test for the loader script. First thought to spy on the registerLoader() method but since it's esm you can't spy on it with sinon. So that would require either an extra depedency to do some sort of mocking, or a refactor of the script...

[pragmaticivan]

Honestly, the change LGTM, it's simple enough, maybe worth including a comment pointing to the change in the AWS blog post. But other than that, LGTM.

[wpessers]

@pragmaticivan That's a good point, it should probably be more clear in the code why we do this check. However I'm not sure there's any official AWS source on this change in the runtime. Rereading the node 24 runtime announcement from AWS I don't see this information in there (or anything hinting at it). @maxday Could you shed any light here, or point to any official resource (if exists) that we can link back to?

[pragmaticivan]

@pragmaticivan That's a good point, it should probably be more clear in the code why we do this check. However I'm not sure there's any official AWS source on this change in the runtime. Rereading the node 24 runtime announcement from AWS I don't see this information in there (or anything hinting at it). @maxday Could you shed any light here, or point to any official resource (if exists) that we can link back to?

https://aws.amazon.com/blogs/compute/node-js-24-runtime-now-available-in-aws-lambda/

Removing support for callback-based function handlers

I think that's the breaking change but not really sure

[wpessers]

I would think the esm loading is kind of orthogonal to the removal of callback support. The blog post does mention something removal of legacy features in general in the new runtime interface client, so maybe this also involves standardization of module loading logic but I can only guess.