Update x/net, x/crypto, x/text and grpc to fix CVEs

What does this MR do?

• Updates golang.org/x/net to v0.60.0, golang.org/x/crypto to v0.57.0, golang.org/x/text to v0.42.0 and google.golang.org/grpc to v1.83.2. No source changes; go mod tidy carries the other golang.org/x modules and OpenTelemetry along.
• Adds the entry to the open, untagged v0.16.2-gitlab.65 section, so version/version.go is unchanged.

Why was this MR needed?

Container scanning flags these modules in the bundled docker-machine binary — 14 CVEs and one advisory:

• gitlab-org/gitlab-runner#39969 — CVE-2026-56852 (x/text)
• gitlab-org/gitlab-runner#39970 — CVE-2026-46600 (x/net)
• gitlab-org/gitlab-runner#39971 — CGA-xx3f-6h82-7qp3 (grpc)
• gitlab-org/gitlab-runner#39988 — CVE-2026-56854 (x/crypto)
• gitlab-org/gitlab-runner#39989 — CVE-2026-84304 (grpc)
• gitlab-org/gitlab-runner#39991 — CVE-2026-56855 (x/crypto)
• gitlab-org/gitlab-runner#39993 — CVE-2026-78662 (x/crypto)
• gitlab-org/gitlab-runner#39994 — CVE-2026-84445 (grpc)
• gitlab-org/gitlab-runner#39995 — CVE-2026-84303 (grpc)
• gitlab-org/gitlab-runner#40018 — CVE-2026-56851 (x/text)
• gitlab-org/gitlab-runner#40077 — CVE-2026-78659 (x/net)
• gitlab-org/gitlab-runner#40078 — CVE-2026-78669 (x/net)
• gitlab-org/gitlab-runner#40081 — CVE-2026-78663 (x/net)
• gitlab-org/gitlab-runner#40083 — CVE-2026-97032 (x/net)
• gitlab-org/gitlab-runner#40091 — CVE-2026-78660 (x/net)

What's the best way to test this MR?

Built ./cmd/docker-machine from main and from this branch and scanned each with trivy rootfs: 22 findings before, 7 after, all 14 tracked CVEs cleared and none introduced. CI's policy-injected dependency scanning covers go.mod; the trivy check covers the compiled binary, which is what the runner image scanners read.

x/crypto/ssh is the only bump with behavioural risk (tightened default algorithms), so driver provisioning against real VMs is where a regression would show.