fix: Add ESM unwrapping to all CommonJS require calls

[kitten]

Summary

This was added to loadConfig.js but is missing in other places. While it's arguably not useful in many cases in a "standard" Metro setup with Metro's own packages, it'd be nice to have this behave consistently even with transpiled ESM output (or with require-ESM in Node).

Specifically this affects:

• metro-file-map plugin workers that are loaded with require
• metro-file-map's main worker loading
• metro's asset plugins
• metro-transform-worker's getMinifier implementation
• metro-transform-worker's babelTransformerPath loading

This is probably specifically interesting for babelTransformerPath which is often overridden by third-party setups.

Changelog: [Fix] Unwrap ES modules when requiring metro-file-map workers, asset plugins, the minifier, or the babel transformer

Test plan

• n/a: This will likely be best left untested, but is a consistent implementation that matches ESM->CJS semantics, also used in loadConfig.js

[meta-codesync]

@robhogan has imported this pull request. If you are a Meta employee, you can view this in D102510513.

[kitten]

Spotted on a re-review that getCacheKey below means that we should be doing:

const getCacheKey =
  mod?.getCacheKey ??
  (mod.__esModule === true && 'default' in mod ? mod.default : mod).getCacheKey;

[meta-codesync]

@robhogan merged this pull request in 0e9d7aa.