[main] Update dependencies from dotnet/runtime dotnet/efcore
- Fixup nullability warnings
- Secret mission to make templates verbose again
- Update template tests to capture information (#37447)
* Update template tests to capture information
* Remove unwanted files
* Update SPA submodule with nullability fixes
* [main] React to dotnet/runtime#57816 (#36155)
- `cherry-pick` e58a6c2465
- see https://github.com/dotnet/runtime/pull/57816#issuecomment-912755824
- also reacting to dotnet/runtime#58731
- undo much of 18a61fb96c
* [main] Cleanup remaining SSP references (#36248)
- `cherry-pick` 888e03a418
- remove references to System.Security.Permissions and its closure
- only mentions are in eng/PackageOverrides.txt and eng/PlatformManifest.txt
- those files will remain unused until we update them in the run-up to 6.0.1
- may see some package refs for SSP and its closure elsewhere but this does not impact targeting pack content
- also remove duplication between `@(AspNetCoreReferenceAssemblyPath)` additions (for efficiency)
nit: Only need to exclude System.Net.Quic from `@(_AvailableRuntimeRefAssemblies)`
- Crypto.Pkcs is **not** present in the transport package
- other disallowed entries aren't present in the transport package or our dependency closure
* Pin analyzers that ship in the SDK
ASP.NET Core produces a few analyzer assemblies that are shipped as part of the .NET SDK. These analyzers are added to web projects targeting 3.1 and newer.
In 6.0, we (unintentionally) bumped the version of Microsoft.CodeAnalysis that these projects referenced to a 4.0 version. This causes warnings when opening
a 3.1 or 5.0 app in VS 2019 as it does not support these versions.
Additionally update the version of Microsoft.CodeAnalysis.* packages used in tests, Razor, and framework analyzers that are only expected to run with VS 2020 to a more recent build. This is largely book-keeping, but allows us
to write a test for file scoped namespaces.
Fixes https://github.com/dotnet/aspnetcore/issues/36552