[breaking change] dotnet format should return a nonzero exit code for unrecognized argument to --diagnostics

### Context
[`dotnet format`](https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-format) is part of the .NET SDK starting .NET 6. One of its command line options is `--diagnostics`:
> `--diagnostics `
>
> A space-separated list of diagnostic IDs to use as a filter when fixing code style or third-party issues. Default value is whichever IDs are listed in the `.editorconfig` file.

### Problem
Currently, `dotnet format --diagnostics DOES_NOT_EXIST` returns an exit code of `0` when the argument to the `--diagnostics` argument is a diagnostic that .NET doesn't know about. However, this is not consistent with the rest of the `dotnet` CLI, which returns `1` for unrecognized arguments. (e.g. `dotnet tool install -g dotnetsay --verbosity SUPER_VERBOSE` or `dotnet build -f net3141592`).

### Notes
- I don't know whether this is feasible because this requires all analyzers to report back whether they know about a particular diagnostic.
- I became aware of this inconsistent behavior because I was running `dotnet format --diagnostics IDE0290` on a machine that didn't have the .NET 8 SDK installed. 🤦