Fix unsigned integer types (UInt16, UInt32, UInt64) display in event viewer

[Copilot]

Problem

Event properties with unsigned integer types (UInt16, UInt32, UInt64) were being displayed as their signed equivalents (short, int, long) in the event viewer. This caused issues when viewing events with large unsigned values, which would appear as negative numbers.

For example, a ulong value like

Original prompt

---

This section details on the original issue you should resolve

<issue_title>ulong event property is displayed as long in event viewer.</issue_title>
<issue_description>I have a method to write ulong event in my event source:

    [NonEvent]
    private unsafe void WriteEvent(int eventId, ulong arg1)
    {
        if (IsEnabled())
        {
            EventData* descrs = stackalloc EventData[1];
            descrs[0] = new EventData { DataPointer = (IntPtr)(&arg1), Size = 8 };
            WriteEventCore(eventId, 1, descrs);
        }
    }

Yet it is still displayed as a long value inside the events grid view.

Is this expected behavior or fixable?</issue_description>

Comments on the Issue (you are @copilot in this section)

@brianrob I am not surprised at this. Looking at the code - at a minimum, this is coming from the `PayloadFetch` struct, which converts incoming signed and unsigned types into their signed .NET equivalents.

I am not sure how easy this is to fix, but I would hope relatively simple. Let's start with copilot trying to update PayloadFetch to differentiate between signed and unsigned types and see if that solves the problem.

Copilot: Please focus specifically on changing the handling of UInt16, UInt32, and UInt64. Don't touch UInt8. You should be able to update the switch statement to set the .NET type to be the unsigned type that matches the input type, rather than translating to the signed .NET type.</comment_new>
<comment_new>@brianrob
@tomuxmon would you mind testing #2315 and see if that fixes your issue?</comment_new>

Fixes #2309

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[brianrob]

Closed in favor of #2315.