Bump TraceEvent package version

[mdh1418]

Fixes #107315

This PR aims to bump the TraceEvent package version to include the changes introduced by microsoft/perfview#2111 which prevents "System.Private.CoreLib" module names associated with TraceEvents from being incorrectly trimmed to "System.Private".

[mdh1418]

It looks like the profiler runtime tests are failing because of a project reference issue. After bumping to a newer TraceEvent library, the Microsoft.Diagnostics.NETCore.Client assembly references are no longer making it to the profiler test's directory

Left side with TraceEvent version bump vs. Right side without TraceEvent version bump

I'm not exactly sure what is preventing Microsoft.Diagnostics.NETCore.Client from being copied into the test directory, but my current suspicion is that Microsoft.Diagnostics.Tracing.TraceEvent began depending on Microsoft.Diagnostics.NETCore.Client sometime after version 3.1.7 because of microsoft/perfview#1867, so building with a TraceEvent package that contains that reference will cause two Dependencies on Microsoft.Diagnostics.NETCore.Client (one with version 0.0.0.0 and another with version 0.2.10.10501), where the latter will prevail.

@hoyosjs Do you have any ideas on how to fix this?

[hoyosjs]

Easiest one is to always assign a high version to the in-tree one and say that one needs to be backward compatible with the one referenced in tests (and it's closure)