Provide extra overloads where methods can accept EX struct values.

Actual behavior

Apologies in advance; I logged this feature request as a bug by mistake...

Say for RtlGetVersion() or CreateProcess(), these methods can accept OSVERSIONINFOEXW and STARTUPINFOEXW values, but because there's no friendly overloads to accept them, the caller is forced to use the direct P/Invoke and play with pointers to get the data through.

Expected behavior

That friendly overloads be provided to accept these EX struct values to manage the process for the caller without needing them to do fixed statements and casting down to OSVERSIONINFOW, etc.

Repro steps

1. NativeMethods.txt content:

RtlGetVersion
CreateProcess

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

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

internal unsafe static NTSTATUS RtlGetVersion(out OSVERSIONINFOEXW lpVersionInformation)
{
    lpVersionInformation = new() { dwOSVersionInfoSize = (uint)Marshal.SizeOf<OSVERSIONINFOEXW>() };
    fixed (OSVERSIONINFOEXW* lpVersionInformationLocal = &lpVersionInformation)
    {
        NTSTATUS res = Windows.Wdk.PInvoke.RtlGetVersion((OSVERSIONINFOW*)lpVersionInformationLocal);
        if (res != NTSTATUS.STATUS_SUCCESS)
        {
            throw ExceptionUtilities.GetExceptionForLastWin32Error((WIN32_ERROR)Windows.Win32.PInvoke.RtlNtStatusToDosError(res));
        }
        return res;
    }
}

Context

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

Start with the NativeMethods.txt entries for RtlGetVersion and CreateProcess and reproduce the provided C# overload scenario. Determine where generated APIs handle OSVERSIONINFOEXW and STARTUPINFOEXW values; done means callers can pass those EX structs without fixed statements, pointer manipulation, or casts to the non-EX types.