Add a new CompilationOption "ReportSuppressedDiagnostics" to enable reporting compiler diagnostics suppressed in source. Note that the command line compilers will report such suppressed diagnostics in the SARIF errorlog file but not on the console output.

This new compilation option was approved by the design team.

Fixes #5216

The portable tooling expects this package is added to portable projects,
but it wasn't in these.

Primary issue is that we currently try to force complete and decode SuppressMessageAttributes in the analyzer callbacks to report a diagnostic. We need to decode these attributes to apply source suppressions to reported diagnostics. However, force completing attributes can lead to us binding more symbols, and subsequently generating more symbol declared events and attempting to callback into the analyzer again.

Fix is to decode the suppress message attributes as a post pass in the analyzer driver and avoid any symbol force completion during analyzer callbacks to report diagnostics.

Fixes #4858

Emit "isSuppressedInSource" boolean property for diagnostics in the ErrorLog file and report suppressed analyzer diagnostics in the error log.

1. CompilationWithAnalyzers can now report analyzer diagnostics with source suppressions (pragma/SuppressMessageAttribute). This will eventually allow us to surface diagnostics with source suppressions in the error list. Note that the behavior of command line compilers and all the GetDiagnostics APIs is unchanged, only the compiler analyzer will report diagnostics with source suppressions.

2. Add FixAll support for Suppression code fixes. Light bulb suppression fixes now show the "Fix all occurrences" options for Document/Project/Solution. This change adds the basic functionality to bulk suppress diagnostics. This will eventually be consumed for baselining all/selected diagnostics from error list/solution explorer.

3. Simplify the Suppression light bulb menu to remove the option to add a local SuppressMessageAttribute. The only options now are to suppress in source (pragma) or suppressions file (assembly level SuppressMessageAttribute).

The native compiler handled corrupted default parameter values by
substituting in default(T).  It's unclear if this was intentional
behavior in the compiler or not.

Either way though obfuscators took advantage of this behavior and at
least one prominent one will corrupt default parameter values when the
value is null.  Enough prominent libraries have shipped using such
obfuscators that it is a blocker to upgrading.  Hence we need to emulate
the native compiler behavior here.

This change is a bit large because I needed to update the test resources
with a corrupted DLL in order to test out the changes.

closes #4196

Fixup tests (which now show better error recovery).

Report a diagnostic if an analyzer reports a diagnostic with an invalid ID (has non-alphanumeric characters).

Move TestUtilities.csproj and TestUtilities.FX45.csproj to separate directories to accomodate current nuget limitations

Don't skip executing analyzer compilation actions in the IDE when ClosedFileDiagnostics flag is turned off OR the analyzer reports only hidden diagnostics. Compilation actions and compilation end actions can report diagnostics on open files, so they must always be executed.

Fixes #4068

It looks like MSBuild on Mono resolves hardcoded relative paths
in "Include" clauses as being relative to the framework install
location instead of the the project file location.