Remove CryptoConfigForwarder et al.

[teo-tsirpanis]

This class does not seem to be necessary after the unification of the crypto assemblies. I also fixed a typo and did some minor clean-up.

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/area-system-security, @bartonjs, @vcsjones
See info in area-owners.md if you want to be subscribed.

Copilot reviewed 5 out of 9 changed files in this pull request and generated no comments.

Files not reviewed (4)

• src/libraries/System.Security.Cryptography/src/System.Security.Cryptography.csproj: Language not supported
• src/libraries/System.Security.Cryptography/src/System/Security/Cryptography/CryptoConfig.Common.cs: Evaluated as low risk
• src/libraries/System.Security.Cryptography/src/System/Security/Cryptography/CryptoConfigForwarder.cs: Evaluated as low risk
• src/libraries/System.Security.Cryptography/src/System/Security/Cryptography/KeyedHashAlgorithm.cs: Evaluated as low risk

Comments suppressed due to low confidence (1)

src/libraries/System.Security.Cryptography/src/System/Security/Cryptography/CryptoConfig.cs:16

• [nitpick] The error message string 'CreateFromNameUnreferencedCodeMessage' could be clearer. Consider rephrasing to 'The default algorithm implementations might be removed. Use strong type references like 'RSA.Create()' instead.'

internal const string CreateFromNameUnreferencedCodeMessage = "The default algorithm implementations might be removed, use strong type references like 'RSA.Create()' instead.";