setcap on Node.js prevents processing of NODE_OPTIONS

<!-- Thank you for reporting an issue. This issue tracker is for bugs and issues found within Node.js core. If you require more general support please file an issue on our help repo. https://github.com/nodejs/help Please fill in as much of the template below as you're able. Version: output of `node -v` Platform: output of `uname -a` (UNIX), or output of `"$([Environment]::OSVersion | ForEach-Object VersionString) $(if ([Environment]::Is64BitOperatingSystem) { "x64" } else { "x86" })"` in PowerShell console (Windows) Subsystem: if known, please specify affected core module name --> * **Version**: v15.11.0 * **Platform**: Linux connor-Virtual-Machine 5.4.0-66-generic * **Subsystem**: unknown ### What steps will reproduce the bug? 1. `sudo setcap cap_net_admin+iep $(which node)` 2. Attempt to use anything in the NODE_OPTIONS environment variable 3. Nothing happens ### How often does it reproduce? Is there a required condition? 100% of the time ### What is the expected behavior? I would expect NODE_OPTIONS to be processed regardless. ### What do you see instead?  ### Additional information Reported on https://github.com/microsoft/vscode-js-debug/issues/852