feat: add default DEBUG and VERBOSE_LOGS configuration_env_vars to nodejs_binary

[gregmagolan]

• all rules updated to use DEBUG and VERBOSE_LOGS environment variables
• added golden_debug attribute golden_file_test to support the case where a rule has different output if DEBUG is set; for example

golden_file_test(
name = "test",
actual = "out.min.js",
golden = "output.golden.js_",
golden_debug = "output.debug.golden.js_",
)

[alexeagle]

We should figure out how --config=debug relates to --define=DEBUG=1
Maybe they can be the same meaning, and we update the .bazelrc to include the --define flag in --config=debug - that's how I imagined this working. Then users have only one thing to learn.
OTOH it means that you get breakpoints in your node programs and also get different rule outputs, but maybe you only wanted one of those things to happen.

Needs some documentation somewhere - ideally there should be "if something is wrong with your Bazel build, include --config=debug in your command line, find the log file at /some/path and check it for confidential info, then send to us to help diagnose your problem" (not that users read all docs before filing but at least we can point them to that when we have trouble responding to an issue)

[gregmagolan]

I'll add some docs to the main readme for these settings. I think we can recommend that user's add

test:debug --test_arg=--node_options=--inspect-brk --test_output=streamed --test_strategy=exclusive --test_timeout=9999 --nocache_test_results --define=VERBOSE_LOGS=1
run:debug --define=VERBOSE_LOGS=1
build:debug --define=DEBUG=1

to the bazelrc in the docs and explain what each flag does including the two define flags. User's can then choose to exclude certain flags such as build:debug --define=DEBUG=1 if they don't want --config=debug to affect their build.

Also, I think VERBOSE_LOGS may be better than DEBUG_LOGS as per your slack comment.

[alexeagle]

hmm, I'm not sure it's worth adding CI load for this. let's just turn on these options in all our builds? I think spammy is probably good so we can understand CI failures for all jobs?

[gregmagolan]

Since - "--define=DEBUG=1" changes build output I think we need to run all tests without it set and with it set. No other way to know if the rules that change their output based on this break things.

[alexeagle]

I guess this is the one bit of coverage we miss if we don't have a mix of debug/non-debug jobs. Not convinced it's needed since the debug attribute covers like 80% of the feature

[alexeagle]

yeah I guess that's the principled thing... kinda annoying though