nodeOptions passed both to wrapper process as the service process

All arguments set in `nodeOptions` are used to execute the wrapper service and then reused, to call the service itself.

If `--inspect` or `--inspect=` (where portnum !=0) is provided as nodeOptions it prevents from starting the service, as the wrapper process is already bound to desired port.

My expectations is that `nodeOptions` should be passed only to the service nodejs process and not at all to wrapper process or at least there should be a way to provide `nodeOptions` that will be used only by service process and not by wrapper process.

No files or tests are named. Trace where nodeOptions are applied when starting the wrapper and service processes, using the --inspect behavior as the reproduction case; done means service-only options no longer prevent the wrapper and service from starting.

Written by the indexing model from the issue text.