The P/Invoke `NetGetAadJoinInformation()` doesn't generate a SafeHandle overload.

Happy new year, Jevan! This might be a win32metadata thing, I'm not too sure.

Actual behavior

The documentation for NetGetAadJoinInformation() states:

You must call the NetFreeAadJoinInformation function to free the memory allocated for this structure.

The current friendly overload is generated is:

internal static unsafe winmdroot.Foundation.HRESULT NetGetAadJoinInformation([Optional] string pcszTenantId, out winmdroot.NetworkManagement.NetManagement.DSREG_JOIN_INFO* ppJoinInfo)
{
    fixed (winmdroot.NetworkManagement.NetManagement.DSREG_JOIN_INFO** ppJoinInfoLocal = &ppJoinInfo)
    {
        fixed (char* pcszTenantIdLocal = pcszTenantId)
        {
            winmdroot.Foundation.HRESULT __result = PInvoke.NetGetAadJoinInformation(pcszTenantIdLocal, ppJoinInfoLocal);
            return __result;
        }
    }
}

Expected behavior

With the above in mind, I'd expect to see a NetFreeAadJoinInformationSafeHandle type being generated.

Repro steps

1. NativeMethods.txt content:

NetGetAadJoinInformation

2. NativeMethods.json content (if present): N/A

3. Any of your own code that should be shared? N/A

Context

• CsWin32 version: 0.3.264
• Win32Metadata version (if explicitly set by project): N/A
• Target Framework: net472
• LangVersion (if explicitly set by project): N/A

Start with the generated NetGetAadJoinInformation overload and reproduce the issue using a NativeMethods.txt containing that API. Trace how CsWin32 determines ownership and generates friendly overloads, then verify that a NetFreeAadJoinInformationSafeHandle is generated and corresponds to the documented cleanup requirement.