Support displaying AttributeValue in binary form

[vcsjones]

If an X500DistinguishedName contains an AttributeValue that is not a DirectoryString, the managed decoder will currently throw, catch the error, and return an empty string.

This changes the managed decoding to match the behavior of Windows. If an attribute is a binary value, then it is displayed in a hex encoded value, prefixed with a hash.

There is special handling if the binary value is an OCTET STRING. If the binary content is an octet string, the hex value displayed is the inner content. The outer OCTET STRING bytes are not displayed.

Fixes #88037.

Note: This only changes displaying binary content. Handling the reverse, parsing the strings like new X500DistinguishedName("CN=#1234") will be a separate pull request. That will be a breaking change on non-Windows, and we may decide not to take it. This pull request is not a breaking change and simply unblocks a scenario.

[ghost]

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

Issue Details

---

If an X500DistinguishedName contains an AttributeValue that is not a DirectoryString, the managed decoder will currently throw, catch the error, and return an empty string.

This changes the managed decoding to match the behavior of Windows. If an attribute is a binary value, then it is displayed in a hex encoded value, prefixed with a hash.

There is special handling if the binary value is an OCTET STRING. If the binary content is an octet string, the hex value displayed is the inner content. The outer OCTET STRING bytes are not displayed.

Author:	vcsjones
Assignees:	vcsjones
Labels:	area-System.Security
Milestone:	-

[vcsjones]

Test failure is being tracked by #88172. Merging.