fix: use require for import in the middle

[dyladan]

Fixes an issue where bundlers (esbuild) fail to build because of es module interop issues.

Import in the middle does not have a default export, which means import IITM from 'import-in-the-middle'; fails. Importing as a namespace with import * as IITM from 'import-in-the-middle'; works, but causes issues with bundlers. Specifically, namespace imports are required by the ESM spec to be objects. IITM's top-level export is not an object, but a callable function (https://github.com/DataDog/import-in-the-middle/blob/c3c2c52c1915b47994af59d507c59029c1f1fae9/index.js#L91).

This draft is to consider the possibility of using require instead of import for this dependency.

Related to #4519

[codecov]

Codecov Report

Merging #4546 (6ffda27) into main (3a426e8) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #4546   +/-   ##
=======================================
  Coverage   92.83%   92.83%           
=======================================
  Files         328      328           
  Lines        9486     9486           
  Branches     2035     2035           
=======================================
  Hits         8806     8806           
  Misses        680      680