React to changes in ApiCompat and re-baseline

[rladuca]

ApiCompat was altered to add support for member level attribute checks (see dotnet/arcade@2fdcfc2#diff-9b7e2af6cbe16f7c69be4a9cc5ae4418)

Due to this change, WPF needs to examine and re-baseline its ApiCompat errors. We should also update to the latest exclusions being used in dotnet/runtime since that will help reduce the set of errors.

This is blocking flow from Arcade in this PR: #2175

This work will be based on the Arcade flow above, but I am using this issue as a record of the reasoning behind various baselines.

[rladuca]

ExcludingSecurityTreatAsSafeAttribute as these are no longer in use.

[rladuca]

Excluding CommonDependencyPropertyAttribute as this is only used in internal generation of https://github.com/dotnet/wpf/blob/master/src/Microsoft.DotNet.Wpf/src/PresentationFramework/System/Windows/Markup/KnownTypes.cs and is not needed in the reference assembly.

[rladuca]

Much of the noise here is CannotChangeAttribute errors. These are generally due to conversion from some enumeration in the implementation to the equivalent numerical value in the reference assembly (GenAPI does this). These can all be baselined away (as we've done before) and will significantly reduce noise.

[rladuca]

MS.Internal.CustomCategoryAttribute
System.Windows.CustomCategoryAttribute
System.ComponentModel.DefaultValueAttribute

Can all be baselined, the designer looks at implementation, not reference assemblies.