Runtime analyzers now reference Roslyn 4.14.0.0 and fail to load in some hosts

[ericstj]

As of #119195 all the runtime-provided source-generators / analyzers now target roslyn 4.14.0.0.

This broke their use in DocFx, since the latest shipping version is still bundling 4.12.0.0 -- and there's no override.

That PR mentions:

Low. Analyzer-only fix. Note that it does include an update to Microsoft.CodeAnalysis, which needs to remain compatible with the version that ships with VS. Confirmed with @jkoritzinsky that this version is OK for .NET 10.

We should double check this @jkoritzinsky @ViktorHofer. If possible we should be making these changes much earlier in the release.

[jkoritzinsky]

We try to make these changes earlier in the release. In this case, the trimming analyzer needed to react to new APIs introduced in Roslyn very late in the release.

If we have additional constraints on upgrading the Roslyn version used by analyzers (like DocFx), then we need to update the guidance we have in eng/Versions.props to account for these constraints (as the only constraint we have documented today is innerloop dev experience)

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.