Correct `node -h` text for `-r, --require` option

[juergba]

Version

v14.17.0

Platform

Microsoft Windows NT 10.0.19043.0 x64

Subsystem

No response

What steps will reproduce the bug?

node -h

How often does it reproduce? Is there a required condition?

always

What is the expected behavior?

-r, --require <module>          module to preload (option can be repeated)

What do you see instead?

-r, --require=...          module to preload (option can be repeated)

Additional information

This is just a nit. The "=" is confusing, or even wrong with -r=foo:

• ok: --require=foo
• ok: --require foo
• fails: -r=foo
  => C:\Program Files\nodejs\node.exe: bad option: -r=foo
• ok: -r foo

The command-line options docs shows no "=" sign: -r, --require module
The behavior of this option isn't consistent, also compared to the rest of Node's CLI options.

[juergba]

The output of node --v8-options shows:

The following syntax for options is accepted (both '-' and '--' are ok):
  --flag        (bool flags only)
  --no-flag     (bool flags only)
  --flag=value  (non-bool flags only, no spaces around '=')
  --flag value  (non-bool flags only)
  --            (captures all remaining args in JavaScript)

• fails without "=": eg. node --wasm-max-code-space 1024
  => Error: illegal value for flag --wasm-max-code-space of type uint
• ok with "=": node --wasm-max-code-space=1024