quic-go versions are skewed across the two ends of the same connection

Summary

The worker and the proxy sit at opposite ends of the same QUIC connection and are pinned six minor versions apart, both behind current.

Why now

This surfaced while investigating stateful session failures. It is not a suspected cause of that incident: the release notes between v0.54 and v0.61 contain no idle-timeout or keep-alive fix, and no public API for path migration or changing a connection's local address.

The reason to do it is the skew itself. Client and server on the same connection should not be six versions apart, and the gap only widens.

Prerequisite is already met

v0.60 and later require Go 1.25. All three modules already declare go 1.25.0, so unification on v0.61.0 is unblocked.

Inspect the go.mod files in src/libraries/go/worker, src/invocation-plane-services/grpc-proxy, and src/compute-plane-services/worker-utils, starting with their quic-go requirements. Align the worker and proxy dependencies on v0.61.0, confirm the indirect worker-utils dependency resolves consistently, and run the relevant Go tests for these modules.