Improve startup and runtime performance by removing XamlTypeInvoker dead code

[ThomasGoulet73]

Description

Removes XamlTypeInvoker dead code. This code is hit when creating an instance of a non-known type from XAML/BAML. Removing this code improves both startup and runtime performance.

Known types are types in an hard-coded list that makes them more optimized by WPF. This includes types from WPF and some BCL common types (Like int, bool, string, etc). Everything else is a non-known type so things like custom controls are non-known types.

The reason this is dead code is because DefaultCtorXamlActivator.EnsureConstructorDelegate always returns false because of this condition here:

wpf/src/Microsoft.DotNet.Wpf/src/System.Xaml/System/Xaml/Schema/XamlTypeInvoker.cs

Line 330 in e500f8e

if ((tConstInfo.IsSecurityCritical && !tConstInfo.IsSecuritySafeCritical) ||

Since the removal of CAS from .Net, ConstructorInfo.IsSecurityCritical always returns true and ConstructorInfo.IsSecuritySafeCritical always returns false so the the condition is always true which means that the whole DefaultCtorXamlActivator class doesn't do anything.

Here's the .Net code for ConstructorInfo.IsSecurityCritical and ConstructorInfo.IsSecuritySafeCritical which always return constants:
https://github.com/dotnet/runtime/blob/a349912e4f8610f39a6ac3cb73d8d4d0968ccec4/src/coreclr/System.Private.CoreLib/src/System/Reflection/RuntimeConstructorInfo.CoreCLR.cs#L228-L230

Benchmarks

I benchmarked a new WPF from the Visual Studio template where I added an empty class like public class CustomLabel : Label { } and I added this control 20 times in the XAML of the main window. This PR shaves about 30-40 ms when starting the app.

There's a small cache per-type that skips some of the code so I also benchmarked a new WPF from the Visual Studio template where I added 20 empty classes like public class CustomLabel1 : Label { } and I added each control in the XAML of the main window. This PR shaves about 50-60 ms when starting the app.

I expect more complex apps with more non-known type in XAML to have even bigger performance gain. Projects that have a ton of non-known types are third-party control vendors (Like DevExpress, Telerik, etc) because they have a ton of custom controls.

Customer Impact

Better startup and runtime performance.

Regression

No.

Testing

Local testing using sample app that hits this specific code.

Risk

Low.

Microsoft Reviewers: Open in CodeFlow

[ThomasGoulet73]

I rebased to fix the conflicts.

[ThomasGoulet73]

I rebased to fix the conflicts.

[ThomasGoulet73]

I rebased on main to fix the conflicts.