…building the DFA tree to trim unnecessary nodes (#33712)

* Performs filtering of nodes while building the DFA matcher by evaluating literal nodes against parameter constraints and complex segments and discarding those that would never have produced a match.
* Introduces a new interface that allows parameters to filter literal candidate nodes based on the parameter name or the literal node value
* Implements the new interface in all our route constraints.

[main] Update dependencies from dotnet/efcore dotnet/runtime

As part of hot reload, types marked with `CreateNewOnMetadataUpdateAttribute` will result in a new type created rather than updating existing types. This works really well for .cshtml scenario where the type is never referenced by name, but rather using the path. This change adds the annotation to the cshtml file and does the runtime work to substitute the build-time compiled file with hot reloaded type on a hot reloaded event. 

* Annotate cshtml files with `CreateNewOnMetadataUpdateAttribute` when targeting RazorLangVersion = 6.0
* Additionally annotate cshtml files with an `RazorCompiledItemMetadataAttribute attribute that identifies the path (identifier)
* Update RazorCompiledItemFeatureProvider to substitute a compiled type with a hot reloaded type
* Clear more Razor specific caches as part of a hot reload event

Fixes #34248

* Implement GetClientCertAsync, ApplicationProtocol

* Update src/Servers/Kestrel/Transport.Quic/src/Internal/QuicConnectionContext.FeatureCollection.cs

Co-authored-by: Chris Ross <[email protected]>

* Update src/Servers/Kestrel/Transport.Quic/src/Internal/QuicConnectionContext.FeatureCollection.cs

Co-authored-by: Chris Ross <[email protected]>

* Undo ITlsApplicationProtocolFeature

* Feedback

* Add (failing) test

* Remove d.l

* Fix test

* Fix

* Update src/Servers/Kestrel/Transport.Quic/test/QuicConnectionContextTests.cs

Co-authored-by: James Newton-King <[email protected]>

* Skip on non-win

Co-authored-by: Chris Ross <[email protected]>
Co-authored-by: James Newton-King <[email protected]>

* Remove GetCallingAssembly usage
- Today the WebApplicationBuilder tries to guess what the application name should be based on the immediate caller of the API using Assembly.GetCallingAssembly. This is because several components use the application name as a way to find the application assembly in order to do other things;
- User secrets uses it to find the location of the  directory that holds configuration secrets.
- MVC uses it as the assembly to start the search for controllers, pages, etc.
- Identifty uses it to find application parts.
This API is a bit fragile for internal refactoring (if the immediate caller is anything except for user code, then we will treat our own assembly as the calling assembly) and more importantly, it breaks in NativeAOT scenarios. Instead of the calling assembly, we now default to the entry assembly.
- This will "break" in scenarios where the WebApplication is started in a library and the entry point is the host application (controllers will be scanned in potentially the wrong place by default or it will find the wrong controllers).
- Now that we have the option that allows specifying the name of the application name via WebApplicationOptions, In the future, we're investigating ways that the compiler can inject the calling assembly via an attribute similar to [CallerMemberName] that would capture the calling assembly in a more reliable and AOT friendly way.
- Added a test that asserts that the default application name is the entry assembly.
- Updated the slnf file

* PR feedback
- Change the name of the overriding assembly since the entry assembly is the default.

…35045)

#35018

* Use Fedora queue that supports msquic

* Run tests in PR quar

* Quarantine all quic tests

Remove comments left over from code that has since been removed.

* Do not overwrite NoWarn

Do not overwrite the NoWarn property, and instead add to it.

* Do not overwrite NoWarn

Do not overwrite the NoWarn property, and instead add to it.

* Do not overwrite NoWarn

Do not overwrite the NoWarn property, and instead add to it.

[main] Update dependencies from dotnet/efcore

Fixes build break found in dotnet/sdk#19539

…806.1 (#35095)

[main] Update dependencies from dotnet/efcore