doc: add a cli options doc page

[Fishrock123]

Pull Request check-list

• Does make -j8 test (UNIX) or vcbuild test nosign (Windows) pass with
  this change (including linting)?
• Is the commit message formatted according to CONTRIBUTING.md?
• Is a documentation update included (if this change modifies
  existing APIs, or introduces new ones)?

Affected core subsystem(s)

doc

Description of change

This page is mostly a mirror of the updated manual page. This came about as a result of this twitter conversation, and I realized there wasn't an easy way to get the options documentation from the website.

cc @nodejs/documentation

Edit: Rendered (but our css makes it look slightly different)

[cjihrig]

Does this need to be all caps?

[cjihrig]

LGTM with a couple comments.

[jasnell]

LGTM
woohoo!
/cc @nodejs/documentation

[chrisdickinson]

Suggestion:

Node.js comes with a wide variety of CLI options. These options expose multiple ways to execute scripts, built-in debugging, and other helpful runtime options.

[bengl]

Line wrapping is somewhat inconsistent. Perhaps wrap it at 80?

[Fishrock123]

@chrisdickinson Worded it this way so that it didn't sound like "multiple" applied to everything.

[Fishrock123]

@bengl Fixed. I forgot about that when copying from the man page.

[bengl]

@Fishrock123 lines 5 and 154?

[Fishrock123]

Oops, didn't notice my editor was wrapping there, thought I had inserted spaces. Fixed.

[bengl]

Cool, LGTM!

[eljefedelrodeodeljefe]

Yep, nice. LGTM.

[benjamingr]

Awesome work on all the recent docs PRs lately @Fishrock123 !

[benjamingr]

CLI options -> command line options perhaps? Are we sure all the users are familiar with the term? Windows users in particular...

[Fishrock123]

I was hoping that the title would clarify it, but I suppose I can can do this.

[benjamingr]

LGTM with nits. To clarify none of the nits prevent the merge IMO and they can be addressed at a later point or now depending on @Fishrock123's opinion.

[Fishrock123]

I would have liked if some of this feedback was done when I wrote some of these in the man doc refactor. D:

[eljefedelrodeodeljefe]

I'd be against the nits, since it will become inconsistent to node -h. I'd say land now, improve later (IMO don't do anything). Still LGTM.

[benjamingr]

To be clear - I'm in the same opinion of @eljefedelrodeodeljefe of land now merge later.

[Fishrock123]

ok landing this as-is and making a new updating PR

I'm afraid for this there isn't a better way to keep it in sync, formatting differences and other nits vary quite a bit from the --help, node.1, and this document.

[Fishrock123]

Actually, I'm going to add to the comment in https://github.com/nodejs/node/blob/master/src/node.cc#L3296 in this PR also, just to try to help keep them in sync.

[Fishrock123]

Ci, since this now modifies node.cc with a comment: https://ci.nodejs.org/job/node-test-pull-request/1992/

[Fishrock123]

(Also I added a comment about NODE_PATH that only effects windows, which is less necessary in the man page since manual pages don't really exist on windows.

[Fishrock123]

Oops.

Landed in 91cf55b, will make a new PR to fix some of the docs in multiple spots like tomorrow.