Added additional OIDs for CMS signatures.

[vcsjones]

This adds additional OIDs for RSA CMS validation when the OID is specific about which hash algorithm should be used.

This is a slightly different approach from the DSA / ECDsa approach. This allows for a null HashAlgorithmName and does not enforce the hash algorithm if one is not specified when using the "1.2.840.113549.1.1.1" OID.

Fixes #32639

[vcsjones]

/cc @bartonjs @onovotny

[vcsjones]

Hm. Now that I think about it, we can do 1.2.840.113549.1.1.4 for MD5 support. @bartonjs, do we want an MD5WithRsa OID here?

[bartonjs]

the S in signed should be uppercase :)

[vcsjones]

Doh. 🐪

[bartonjs]

@bartonjs, do we want an MD5WithRsa OID here?

Eh, I'd leave it out unless there's a reason to bother later.

[vcsjones]

Eh, I'd leave it out unless there's a reason to bother later.

Makes sense. I have no compelling reason to put it there other than completeness, and I'm not particularly fond of MD5-anything.

Fixed the casing issue.

[bartonjs]

@dotnet-bot Test this please (lots of failures due to what looks like a Jenkins restart)

[bartonjs]

@vcsjones The (valid) test document you added doesn't have indefinite length content, right? (I don't see an 0x24, so it shouldn't be; but making sure I'm not being redundant)

[vcsjones]

@bartonjs no they do not, I didn't want to risk cramming two issues into the same CMS.