*: upgrade to go 1.21.0

[healthy-pod]

• Adjust the Pebble tests to run in new version.
• Adjust version in Docker image (source).
• Adjust version in the TeamCity agent image (setup script)
• Rebuild and push the Docker image (following Basic Process)
• Update build/teamcity/internal/release/build-and-publish-patched-go/impl.sh with the new version and adjust SHA256 sums as necessary.
• Run the Internal / Cockroach / Build / Toolchains / Publish Patched Go for Mac build configuration in TeamCity with your latest version of the script above. Note the job depends on another job Build and Publish Patched Go. That job prints out the SHA256 of all tarballs, which you will need to copy-paste into WORKSPACE (see below). Publish Patched Go for Mac is an extra step that publishes the signed go binaries for macOS. That job also prints out the SHA256 of the Mac tarballs in particular.
• Bump the version in WORKSPACE under go_download_sdk. You may need to bump rules_go. Also edit the filenames listed in sdks and update all the hashes to match what you built in the step above.
• Run ./dev generate bazel to refresh distdir_files.bzl, then bazel fetch @distdir//:archives to ensure you've updated all hashes to the correct value.
• Bump the version in builder.sh accordingly (source).
• Bump the version in go-version-check.sh (source), unless bumping to a new patch release.
• Bump the go version in go.mod.
• Bump the default installed version of Go in bootstrap-debian.sh (source).
• Replace other mentions of the older version of go (grep for golang:<old_version> and go<old_version>).
• Update the builder.dockerImage parameter in the TeamCity Cockroach and Internal projects.
• Ask the Developer Infrastructure team to deploy new TeamCity agent images according to packer/README.md

Release note (build change): upgrade to go 1.21.0
Epic: none

[cockroach-teamcity]

This change is 

[blathers-crl]

It looks like your PR touches production code but doesn't add or edit any test code. Did you consider adding tests to your PR?

_{🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.}

[irfansharif]

Looks like the Go runtime buckets changed in golang/go@87eda2a (cc @sumeerbhola). The new buckets look fine for our purposes though -- we still have the maximum resolution possible for the value ranges (~1ms) we're primarily interested in.

Underlying Go buckets ~1ms range:

bucket[ 50] width=131.072µs          boundary=[655.36µs, 786.432µs)
bucket[ 51] width=131.072µs          boundary=[786.432µs, 917.504µs)
bucket[ 52] width=131.072µs          boundary=[917.504µs, 1.048576ms)
bucket[ 53] width=262.144µs          boundary=[1.048576ms, 1.31072ms)
bucket[ 54] width=262.144µs          boundary=[1.31072ms, 1.572864ms)
bucket[ 55] width=262.144µs          boundary=[1.572864ms, 1.835008ms)
bucket[ 56] width=262.144µs          boundary=[1.835008ms, 2.097152ms)
bucket[ 57] width=524.288µs          boundary=[2.097152ms, 2.62144ms)
bucket[ 58] width=524.288µs          boundary=[2.62144ms, 3.145728ms)

Our resampled buckets with exponential base of 1.1, clamped to range [50us, 100ms]:

bucket[ 16] width=131.072µs          boundary=[655.36µs, 786.432µs)
bucket[ 17] width=131.072µs          boundary=[786.432µs, 917.504µs)
bucket[ 18] width=131.072µs          boundary=[917.504µs, 1.048576ms)
bucket[ 19] width=262.144µs          boundary=[1.048576ms, 1.31072ms)
bucket[ 20] width=262.144µs          boundary=[1.31072ms, 1.572864ms)
bucket[ 21] width=262.144µs          boundary=[1.572864ms, 1.835008ms)
bucket[ 22] width=262.144µs          boundary=[1.835008ms, 2.097152ms)
bucket[ 23] width=524.288µs          boundary=[2.097152ms, 2.62144ms)
bucket[ 24] width=524.288µs          boundary=[2.62144ms, 3.145728ms)
bucket[ 25] width=524.288µs          boundary=[3.145728ms, 3.670016ms)

[RaduBerinde]

Actually most of the lint changes were necessary because of updating honnef.co/go/tools; but it was subsequently updated in #81868. It'd probably be easier to drop all changes to .go files.

[healthy-pod]

do you have time to pick this up soon?

@RaduBerinde Yes this is already in-progress, I should update the PR before Tuesday. We will be upgrading to Go 1.21.0.

[RaduBerinde]

Isn't this file identical to the 1.20 file? If it is, just change the !go1.21 to !go1.22 on that file instead. (and modify the comment on line 11 to say that it was cross-checked against go1.20 and go1.21).

[rickystewart]

Closing in favor of #111928