Update descriptions for strict-related flags

[DanielRosenwasser]

Kind of weird to phrase these in this way, but for most users these are functionally true going forward.

Maybe it would feel less confusing if we said "true as long as strict is still enabled".

[Copilot]

Pull request overview

This pull request updates the default value descriptions for strict-related compiler flags to more accurately reflect their behavior. The change improves clarity by stating that these flags default to true (unless strict is disabled) rather than the previous wording which suggested they default to false (unless strict is set).

Changes:

• Updated the diagnostic message text from "false, unless strict is set" to "true, unless strict is disabled"
• Applied this updated description to all 8 strict-related flags: noImplicitAny, strictNullChecks, strictFunctionTypes, strictBindCallApply, strictPropertyInitialization, strictBuiltinIteratorReturn, noImplicitThis, and useUnknownInCatchVariables
• Updated the test baseline to reflect the new help output

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
src/compiler/diagnosticMessages.json	Updates the diagnostic message definition used for strict flag defaults
src/compiler/commandLineParser.ts	Updates all 8 strict flag options to reference the new diagnostic message
tests/baselines/reference/tsc/commandLine/help-all.js	Updates the baseline to reflect the new default value descriptions in help output

[jakebailey]

Suggested change

	"`true`, unless `strict` is disabled": {
	"`true`, unless `strict` is `false`": {

maybe?