Stop throwing for unsupported options in `Worker`'s `execArgv` and `env.NODE_OPTIONS`.

### Version v17.2.0 ### Platform _No response_ ### Subsystem worker_threads ### What steps will reproduce the bug? Consider this `test.js` file: ```js const { isMainThread, Worker } = require("worker_threads"); if (isMainThread) { new Worker(__filename, { // execArgv: process.execArgv }); } else { console.log("Hello from the worker!", process.execArgv); } ``` > NOTE: `--experimental-json-modules` and `--title` are just examples Run these two commands: ``` node --experimental-json-modules test.js node --experimental-json-modules --title foo test.js ``` They will log ``` Hello from the worker! [ '--experimental-json-modules' ] Hello from the worker! [ '--experimental-json-modules', '--title', 'foo' ] ``` Now, uncomment the `execArgv: process.execArgv` line and run the two commands again. The first command will still log ``` Hello from the worker! [ '--experimental-json-modules' ] ``` however, the second one throws: ``` Error [ERR_WORKER_INVALID_EXEC_ARGV]: Initiated Worker with invalid execArgv flags: --title at new NodeError (node:internal/errors:371:5) at new Worker (node:internal/worker:191:13) at Object.<anonymous> (/home/nicolo/Documenti/dev/babel/babel/test.js:4:3) at Module._compile (node:internal/modules/cjs/loader:1097:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1149:10) at Module.load (node:internal/modules/cjs/loader:975:32) at Function.Module._load (node:internal/modules/cjs/loader:822:12) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) at node:internal/main/run_main_module:17:47 { code: 'ERR_WORKER_INVALID_EXEC_ARGV' } ``` This mans that _the default behavior of the Worker `execArgv` option is not to inherit `execArgv` from the parent thread_ (contrary to what the documentation says). **Why would you want to explicitly pass `execArgv: process.execArgv` anyway?** A few days ago I was trying to implement a require hook that internally uses a `Wor…