deps: upgrade golang.org/x/{crypto,mod,net,sys,text,tools,term}

[andyyang890]

This patch updates the following core dependencies as follows:

• golang.org/x/crypto from v0.6.0 to v0.7.0
• golang.org/x/mod from v0.7.0 to v0.8.0
• golang.org/x/net from v0.7.0 to v0.8.0
• golang.org/x/sys from v0.5.0 to v0.6.0
• golang.org/x/text from v0.7.0 to v0.8.0
• golang.org/x/tools from v0.1.12 to v0.6.0
• golang.org/x/term from v0.5.0 to v0.6.0

Also update rules_go to a compatible version (0.38).

Informs #21001

Release note: None

[cockroach-teamcity]

This change is 

[rafiss]

lgtm!

[knz]

looking at the diffs in each repo,

• golang.org/x/crypto from v0.6.0 to v0.7.0
• golang.org/x/mod from v0.7.0 to v0.8.0
• golang.org/x/net from v0.7.0 to v0.8.0
• golang.org/x/sys from v0.5.0 to v0.6.0
• golang.org/x/text from v0.7.0 to v0.8.0
• golang.org/x/tools from v0.1.12 to v0.6.0
• golang.org/x/term from v0.5.0 to v0.6.0

[knz]

Of these, the upgrade of x/tools is the largest one. It's going to take a little longer to look at.

[knz]

Ok actually most of the changes in x/tools pertain to gopls, which we don't import in crdb. The remaining changes are on the analysis packages. They are all beneficial to us.

[knz]

For references:

• in each of the packages, I ran git log --patch vOLD...vNEW and inspected the results:
  • for any changes to APIs that would impact our code
  • for any impl changes that could impact semantics we care about
  • didn't find anything worrying.
• for x/tools, that was way too many changes, so instead I ran git log --patch vOLD...vNEW | diffstat to first get a sense of which sub-packages saw most movement and focus the review there. This is how I noticed most of the changes were on gopls
• so I re-ran git log vOLD...vNEW -- go/ in x/tools to get just the subset of changes pertaining to the go sub-directory, which is the one we used. Then I inspected that and satisfied myself that none of the changes impact our production code.

[andyyang890]

Thanks for the in-depth review!

bors r=rafiss,knz

[craig]

This PR was included in a batch that timed out, it will be automatically retried

[craig]

This PR was included in a batch that timed out, it will be automatically retried

[craig]

Build succeeded:

• Bazel Essential CI (Cockroach)

[rickystewart]

blathers backport 23.1

[blathers-crl]

Encountered an error creating backports. Some common things that can go wrong:

1. The backport branch might have already existed.
2. There was a merge conflict.
3. The backport branch contained merge commits.

You might need to create your backport manually using the backport tool.

---

error creating merge commit from 161de46 to blathers/backport-release-23.1-103446: POST https://api.github.com/repos/cockroachdb/cockroach/merges: 409 Merge conflict []

you may need to manually resolve merge conflicts with the backport tool.

Backport to branch 23.1 failed. See errors above.

---

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