fix: ESM hooking with Node.js v18.19.0

[trentm]

import-in-the-middle@1.6.0 fixes an issue with double-importing
with node 18.19.0 (due to a backport of ESM loading being done
off main thread).

Fixes: #3784

[trentm]

Sigh. Now we are hitting the other issue in IITM when used with Node.js versions that use off-main-thread ESM loading:
nodejs/import-in-the-middle#29

E.g. from https://github.com/elastic/apm-agent-nodejs/actions/runs/7171406915/job/19526333837?pr=3785

# simple SQS V3 with ESM (fixtures/use-client-sqs.mjs)
not ok 20 fixtures/use-client-sqs.mjs exited successfully: err=Error: Command failed: /opt/hostedtoolcache/node/18.19.0/x64/bin/node fixtures/use-client-sqs.mjs (node:9069) ExperimentalWarning: `--experimental-loader` may be removed in the future; instead use `register()`: --import 'data:text/javascript,import { register } from "node:module"; import { pathToFileURL } from "node:url"; register("../../../../loader.mjs", pathToFileURL("./"));' (Use `node --trace-warnings ...` to show where the warning was created) file:///home/runner/work/apm-agent-nodejs/apm-agent-nodejs/test/instrumentation/modules/@aws-sdk/fixtures/use-client-sqs.mjs:19 CreateQueueCommand, ^^^^^^^^^^^^^^^^^^ SyntaxError: The requested module '@aws-sdk/client-sqs' does not provide an export named 'CreateQueueCommand' at ModuleJob._instantiate (node:internal/modules/esm/module_job:123:21) at async ModuleJob.run (node:internal/modules/esm/module_job:191:5) at async ModuleLoader.import (node:internal/modules/esm/loader:336:24) at async loadESM (node:internal/process/esm_loader:34:7) at async handleMainPromise (node:internal/modules/run_main:106:12) 
  ---
    operator: error
    at: done (/home/runner/work/apm-agent-nodejs/apm-agent-nodejs/test/_utils.js:353:17)
    stack: |-
      Error: Command failed: /opt/hostedtoolcache/node/18.19.0/x64/bin/node fixtures/use-client-sqs.mjs
      (node:9069) ExperimentalWarning: `--experimental-loader` may be removed in the future; instead use `register()`:
      --import 'data:text/javascript,import { register } from "node:module"; import { pathToFileURL } from "node:url"; register("../../../../loader.mjs", pathToFileURL("./"));'
      (Use `node --trace-warnings ...` to show where the warning was created)
      file:///home/runner/work/apm-agent-nodejs/apm-agent-nodejs/test/instrumentation/modules/@aws-sdk/fixtures/use-client-sqs.mjs:19
        CreateQueueCommand,
        ^^^^^^^^^^^^^^^^^^
      SyntaxError: The requested module '@aws-sdk/client-sqs' does not provide an export named 'CreateQueueCommand'
          at ModuleJob._instantiate (node:internal/modules/esm/module_job:123:21)
          at async ModuleJob.run (node:internal/modules/esm/module_job:191:5)
          at async ModuleLoader.import (node:internal/modules/esm/loader:336:24)
       

[trentm]

Ultimately we'll want a fix for that issue -- there is an in-progres PR for that: nodejs/import-in-the-middle#30

Either we sit on this PR, or we could workaround this second issue and avoid testing the affected subset of modules with node v18.19.0. @aws-sdk/client-sqs is one of those modules.

[david-luna]

Either we sit on this PR, or we could workaround this second issue and avoid testing the affected subset of modules with node v18.19.0. @aws-sdk/client-sqs is one of those modules.

As discussed let's make workaround until nodejs/import-in-the-middle#30 is merged and published.

[trentm]

There was a recent IITM commit (nodejs/import-in-the-middle#43) with what I think is a fix for this. It is a very different impl of the issue. I haven't yet had a chance to test whether that fixes the same issue. Also, it isn't yet in an IITM release.

[trentm]

Superseded by #3857