Allow IMallocSpy callbacks during LPSTR/LPWSTR array cleanup

[Copilot]

Interop/COM/ExtensionPoints was failing because the marshaling cleanup path freed CoTaskMem buffers under a NOTHROW contract. When a managed IMallocSpy is registered, CoTaskMemFree can re-enter managed code and violate that contract.

• Cleanup contract fix

  • Update OleVariant::ClearLPSTRArray and OleVariant::ClearLPWSTRArray to use THROWS.
  • This matches the actual behavior of CoTaskMemFree when COM allocation hooks dispatch into managed IMallocSpy implementations.

• Why this addresses the failure

  • The ExtensionPoints test marshals string[] through an unmanaged function pointer, which allocates and later frees LPSTR* buffers.
  • The failure was not in marshaling itself, but in cleanup running with an invalid contract for this callback path.

• Relevant change

void OleVariant::ClearLPSTRArray(void *oleArray, SIZE_T cElements, MethodTable *pInterfaceMT)
{
    CONTRACTL
    {
        THROWS; // CoTaskMemFree can invoke a managed IMallocSpy implementation.
        GC_TRIGGERS;
        MODE_ANY;
        PRECONDITION(CheckPointer(oleArray));
    }
    CONTRACTL_END;
    ...
}

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/interop-contrib
See info in area-owners.md if you want to be subscribed.

[jkotas]

This method is not expected to throw. This contract is correct.

I think this should be fixed by fixing the contracts on the new COM interop implementation. The exceptions are not expected to leak from the COM interop HRESULT-returning methods.