Refactor globals/ErrorSinkCompiler so sarif / other sinks can extend it cleanly

[dkorpel]

SARIF output has been hacked in with global variables and if (global.params.v.messageStyle == MessageStyle.sarif) conditions. Meanwhile there's a WIP ErrorSink refactor that is supposed to cleanly separate custom presentation from errors.d, so here's a refactor to clean up the tangle.

Put the limiting / gating logic in ErrorSinkCompiler,
and make ErrorSinkSarif extend from that, separating it from dmd.errors.
Move enum ErrorKind from errors.d to errorsink.d so error sinks can use it without importing errors.d.

• Remove import dmd.console, dmd.errors from dmd.sarif
• Remove reliance on global.params.v and errors.d
• Remove redundant __gshared Diagnostic[] collection
• Remove redundant struct SarifReport indirection

private extern(C++) void vreportDiagnostic logic is moved into ErrorSinkCompiler. It's private and has no header so I assume it's not used by LDC or GDC. The global gagging/error count, and warning/deprecation as error logic is intact.

This PR is quite big so I can split it up if it's too hard to review or too risky.

[dlang-bot]

Thanks for your pull request and interest in making D better, @dkorpel! We are looking forward to reviewing it, and you should be hearing from a maintainer soon.
Please verify that your PR follows this checklist:

• My PR is fully covered with tests (you can see the coverage diff by visiting the details link of the codecov check)
• My PR is as minimal as possible (smaller, focused PRs are easier to review than big ones)
• I have provided a detailed rationale explaining my changes
• New or modified functions have Ddoc comments (with Params: and Returns:)

Please see CONTRIBUTING.md for more information.

---

If you have addressed all reviews or aren't sure how to proceed, don't hesitate to ping us with a simple comment.

Bugzilla references

Your PR doesn't reference any Bugzilla issue.

If your PR contains non-trivial changes, please reference a Bugzilla issue or create a manual changelog.

Testing this PR locally

If you don't have a local development environment setup, you can use Digger to test this PR:

dub run digger -- build "master + dmd#23176"

[rikkimax]

Feel free to ping me once this is closer to being ready.

I don't trust what I'm seeing atm to approve it.

[dkorpel]

Yeah I'm still figuring out some kinks, there's some funny interactions with stuff like:

-dip25 -de
// Deprecation: `-dip25` no longer has any effect
// (compilation continues)

-de -dip25
// Deprecation: `-dip25` no longer has any effect
// (treated as error)

That is, the error sink can be modified by -v flags after it has been used already to print an error/deprecation for command line parsing.

[thewilsonator]

this would be much easier to review if split into
global.params.v.foo -> global.errorSink.foo (foo = {errorLimit,useWarnings, useDeprecated,showGaggedErrors}) as this changes lots of files and makes the changes to errors, errorsink and sarif much harder to see.

Also the PR title makes this sound like a refactoring of sarif, but it is just as much a refactoring of errors/errorsink. If it is possible to split those changes apart that would be much nicer, failing that please update the PR title and commit messages accordingly.