runtime/trace: v2 traces contain an incorrect timestamp scaling factor on Windows [1.22 backport]

[gopherbot]

@mknyszek requested issue #65997 to be considered for backport to the next 1.22 minor release.

@gopherbot Please open a backport issue for Go 1.22.

[mknyszek]

Forgot to add justification in the main issue. Basically: the fix is incredibly small, simple, and safe. The issue is pretty serious in that traces on Windows just have the completely wrong durations reported (off by a factor of 256) by any and all tooling.

There is a workaround, specifically to set GOEXPERIMENT=noexectracer2. But compared to the size of the fix, that seems needlessly onerous for our users, since it requires rebuilding their programs.

[gopherbot]

Change https://go.dev/cl/570195 mentions this issue: [release-branch.go1.22] runtime: fix EvFrequency event value on Windows in the new tracer

[gopherbot]

Closed by merging abfd578 to release-branch.go1.22.