Add support for ProgID registration (3.0)

[AaronRobinsonMSFT]

Description

Add support for registering a ProgID when a COM class is registered. This only represents the registration part of the work. There is still work to be done in the SDK to generate a .clsidmap file containing a ProgID - dotnet/sdk#3506.

See PR #7551 for post-3.0 release.

Customer Impact

Without this support consumption of COM classes in languages that don't have GUID support is impossible.

Fixes: dotnet/coreclr#25966
Related: https://github.com/dotnet/coreclr/issues/25946

Regression?

COM support is new in 3.0 so this is not a regression from a previous .NET Core release, but is a regression in COM support from .NET Framework using the RegAsm tool.

Risk

Minimal. The registration of ProgIDs is ignored if not requested (backwards compat with previous Preview releases) and registration is following specific COM semantics for mapping a ProgID and CLSID which means there is no impact on any specific .NET Core path.

[AaronRobinsonMSFT]

cc @MeiChin-Tsai @jeffschwMSFT

[wtgodbe]

Branch is open, feel free to merge once this is approved by tactics (CC @danmosemsft in case I forget to bring up core-setup tomorrow)

[AaronRobinsonMSFT]

This has been approved from the CoreCLR perspective.

[danmoseley]

Didn't get tactics OK yet - @vitek-karas is following up

[jeffschwMSFT]

@danmosemsft is the tactics approval based in email, or in person?

[danmoseley]

@jeffschwMSFT @vitek-karas was going to start a thread with you / aaron to get an approval by email. (We didn't do it in the meeting as none of us had enough context to discuss it)

edit: was not Vitek, it was Vivek. Autocomplete. Anyway all sorted out offline.