Core module domain registered as third-party

[mrickard]

Shimmer historically treats the domain module as third-party instrumentation to be lazy-loaded. This is now causing a logged error when the agent attempts to load the nonexistent ./package.json of the core domain module.

Description

Version 11 of the agent uses require-in-the-middle (or import-in-the-middle for ESM); differences in behavior may have eliminated the need to separate out the domain module the way the agent had traditionally done.

Expected Behavior

domain recognized as a core module, with no attempt to load ./package.json.

[workato-integration]

https://new-relic.atlassian.net/browse/NR-179319