--preserve-symlinks-main not respected when using --require and --inspect-brk together

### Version 16.11.0 ### Platform Darwin NAMTJ0390J2KQ 21.6.0 Darwin Kernel Version 21.6.0: Mon Aug 22 20:19:52 PDT 2022; root:xnu-8020.140.49~2/RELEASE_ARM64_T6000 arm64 ### Subsystem internal/modules/cjs ### What steps will reproduce the bug? _No response_ ### How often does it reproduce? Is there a required condition? _No response_ ### What is the expected behavior? That symlinks are preserved for main entrypoint file path resolution when `--require`, `--preserve-symlinks-main`, and `--inspect-brk` flags are all used. ### What do you see instead? When using a symlinked entry point, and calling node with all of `--require`, `--preserve-symlinks-main`, and `--inspect-brk`, the symlink for the entry point is **not** preserved, and the realpath of the entrypoint is used for module loading (and future module loads relative to that entry point). ### Additional information When using `node --require preload.js --inspect-brk thing.js`, `Module.prototype._compile` is entered for `preload.js` before the main entrypoint is loaded. Note the following code block: https://github.com/nodejs/node/blob/main/lib/internal/modules/cjs/loader.js#L1126 ```js if (getOptionValue('--inspect-brk') && process._eval == null) { if (!resolvedArgv) { // We enter the repl if we're not given a filename argument. if (process.argv[1]) { try { resolvedArgv = Module._resolveFilename(process.argv[1], null, false); } catch { // We only expect this codepath to be reached in the case of a // preloaded module (it will fail earlier with the main entry) assert(ArrayIsArray(getOptionValue('--require'))); } } else { resolvedArgv = 'repl'; } } ``` Note especially that `resolvedArgv = Module._resolveFilename(process.argv[1], null, false);` will resolve the main entrypoint filename with the `isMain` arg set to `false`. This will cause `--preserve-symlinks-main` not to be applied for the filename resolution, a…