Support additional friendly names on OID

[vcsjones]

Fixes #36342

Adds the ability for OIDs to support mapping multiple friendly names on non-Windows platforms.

The previous design assumed there was a 1:1 for friendly name <-> OID. I'm not sure if this breaks assumptions elsewhere in the framework.

[ghost]

Tagging subscribers to this area: @bartonjs, @vcsjones, @krwq
Notify danmosemsft if you want to be subscribed.

[vcsjones]

The first commit only changes the dictionary initializer to the cctor builder. The second commit adds additional friendly names.

[bartonjs]

The new ones should just be added in this dictionary...

[bartonjs]

There's already a second dictionary for "this is not the preferred return value for the OID", it should be used instead of a refactoring.

[vcsjones]

@bartonjs I'm not sure I understand. That dictionary doesn't get used for FriendlyName -> OID. It's used in ToFriendlyName which is used to resolve the friendly name from a given OID.

As far as I can tell, the purpose of that dictionary is to allow going from Oid -> FriendlyName, but not FriendlyName -> Oid. For example, on Linux this fails:

var oid = Oid.FromFriendlyName("RSA_KEYX", OidGroup.All);
Console.WriteLine(oid.Value);

But this will print RSA_KEYX:

var oid2 = Oid.FromOidValue("1.3.14.3.2.22", OidGroup.All);
Console.WriteLine(oid2.FriendlyName);

[bartonjs]

Ah. OK, then I guess the refactor makes sense. That one does seem to be for when there's more than one OID that points to the same friendly name (on Windows), not more than one friendly name that points to the same OID. So it supported 1:m, not m:m. Hmm.

I was proven wrong.