cmd/trace/v2: goroutine analysis page doesn't identify goroutines consistently [1.22 backport]

[gopherbot]

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

@gopherbot Please open backport issues for Go 1.21 and Go 1.22. This makes the cmd/trace UI harder to interpret with no easy workaround. The fix is very safe because it only touches debug tooling, specifically go tool trace, not any Go code someone would run in production.

[mknyszek]

This backport only needs to happen for Go 1.22. The relevant codepaths don't exist in Go 1.21. The corresponding 1.21 issue was closed as not planned.

[gopherbot]

Change https://go.dev/cl/562558 mentions this issue: [release-branch.go1.22] cmd/trace/v2,internal/trace: use correct frame for identifying goroutines

[gopherbot]

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