Bad setup for `GetCurrentProcess_SafeHandle()`.

Actual behavior

The wrapper GetCurrentProcess_SafeHandle() returns the current process's handle as a SafeFileHandle. Because the current process's handle is represented as -1, and SafeFileHandle derives itself from SafeHandleZeroOrMinusOneIsInvalid, this means the resulting handle's IsInvalid property is always true.

Expected behavior

The GetCurrentProcess_SafeHandle() wrapper should return a SafeHandle type derived directly from SafeHandle where only 0 is considered invalid.

Repro steps

1. NativeMethods.txt content:

GetCurrentProcess

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.183+73e6125f79.RR]
• Win32Metadata version (if explicitly set by project): N/A
• Target Framework: [net462]
• LangVersion (if explicitly set by project): N/A

Start with the NativeMethods.txt entry containing GetCurrentProcess and inspect the generated GetCurrentProcess_SafeHandle wrapper. Reproduce the net462 case described in the issue and verify that the returned handle treats the current process handle value as valid, with IsInvalid no longer always true.