Disable no-console for CLI config

[noahtallen]

Edit: I've updated this to just clarify the readme.

I used the CLI config in a different repo (see https://github.com/Automattic/vip-go-utility-scripts/pull/477), but was surprised that using console.log still showed warnings. (The readme also implies that this rule is disabled here: https://github.com/Automattic/eslint-config-wpvip?tab=readme-ov-file#cli)

Any objections to disabling the no-console rule for the CLI preset?

[chriszarate]

The reasoning here is a little aspirational, but it's basically this:

1. Calling console.* directly is a primitive way to log, both for "regular" applications and for output in CLI contexts. Ideally you are delegating to something else that calls console.* or process.stdout on your behalf, usually with additional context or adornment. Delegation makes mocking easier so that you don't have to mock and restore a global, and it makes expects easier because you catch more primitive input before it has been adorned or formatted.
2. If we followed the approach of #1, then we still find value in the no-console rule in CLI contexts, to flag accidental debugging logs.

That said, our CLI applications don't really live up to this standard and I think most of them just override it themselves. In general, though, we like to keep the config strict for new projects and to motivate older projects to improve.

This could all be made much more clear, of course, in the README and maybe comments in this preset. If you wanted to add that it would be much appreciated!

[noahtallen]

Yeah, I can update the readme :)

Hm, I think I follow. Seems like this preset is more oriented towards customer-facing CLI tools rather than assorted node scripts, which makes sense.

[chriszarate]

thanks!!