feat: support LoaderContext.loadModule

[CPunisher]

Summary

closes #3738
closes #7723

TODOs or existing bugs to fix:

• Resolver options of referenced modules should extend their parent modules'. Related to https://github.com/web-infra-dev/rspack/blob/833c058da7a9d1c2a15cd9be49065d7c75c7ed7a/tests/webpack-test/cases/loaders/issue-4959/loaders/index.js, "b" is defined in the browser field in package.json, but it's not resolved.
• Handle module cycle. Related to https://github.com/web-infra-dev/rspack/blob/833c058da7a9d1c2a15cd9be49065d7c75c7ed7a/tests/webpack-test/cases/errors/load-module-cycle/index.js. Currently there seems no cycle detection in rspack ([Feature]: Support circular-dependency-plugin #6048).
• Other options that differ from the options of importModule: recursive, connectOrigin, checkCycle

Checklist

• Tests updated (or not required).
• Documentation updated (or not required).

[netlify]

✅ Deploy Preview for rspack canceled.

Built without sensitive environment variables

Name	Link
🔨 Latest commit	b52e30b
🔍 Latest deploy log	https://app.netlify.com/sites/rspack/deploys/66ee760024d7f7000852b0b2

[CPunisher]

@h-a-n-a I have finished the basic implementation except the bugs above. It's more complex than I expect. One key point is to get original module info when importing/loading referenced modules in loaders. But from my inspect, the artifacts that contain module graphs are not shared between the task loop of ModuleExecutor and main task loop. Am I right?

[luhc228]

An exciting feature! I need this API, too.