src: implement runtime option --no-node-snapshot for debugging

[joyeecheung]

Refs: #28558

I did not add any documentation for this flag - the intention is to dedicate it to debugging Node.js core, somewhat similar to --expose-internals and --inspect-brk-node.

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• tests and/or benchmarks are included
• documentation is changed or added
• commit message follows commit guidelines

[devsnek]

Might want to mention it's an undocumented debug flag here.

[Trott]

I think the warnings are alphabetical so this should go above --no-warnings?

[Trott]

Er, well, they aren't alphabetical, but they're mostly alphabetical?

[addaleax]

… if this is supposed to be undocumented, I’d prefer not documenting it at all (i.e. no help text) over documenting that it’s undocumented, because the latter is pretty self-contradictory.

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/24290/

[Trott]

Is --no-snapshot sufficient?

[joyeecheung]

@Trott That can be somewhat ambiguous because there is also the v8 default snapshot, we use --without-snapshot and --without-node-snapshot to distinguish between the two in the configure script.

[addaleax]

… if this is supposed to be undocumented, I’d prefer not documenting it at all (i.e. no help text) over documenting that it’s undocumented, because the latter is pretty self-contradictory.

[addaleax]

This doesn’t really make sense as a per_env option though, right? More as a per-Isolate one?

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/24330/

[joyeecheung]

Removed the help text and moved it into per-isolate options

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/24333/

[joyeecheung]

Landed in 581bddc