Update go mod deps, regenerate /vendor

[dekkagaijin]

Make dependabot & consumers happy. This silences a dependabot vuln alert for containerd which does not affect go-containerregistry but does show up on a scan of our dependency graph.

Generated by:

$ go get -u ./...
$ go mod tidy
$ go mod vendor

[codecov-commenter]

Codecov Report

Merging #1139 (638022a) into main (230ff8e) will not change coverage.
The diff coverage is n/a.

❗ Current head 638022a differs from pull request most recent head ec77da7. Consider uploading reports for the commit ec77da7 to get more accurate results

@@     Coverage Diff      @@
##   main   #1139   +/-   ##
============================
============================

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 230ff8e...ec77da7. Read the comment docs.

[imjasonh]

Can you cite an unhappy consumer today? What's being fixed?

[dekkagaijin]

Can you cite an unhappy consumer today?

Dependabot, at least for containerd/containerd < 1.5.7

[imjasonh]

Your PR description could use some work.

• This looks like a generated change. If it is, how was it generated? go get -u ./...?
  • Knowing roughly the steps it took to make this change helps ensure this isn't going to cause other issues, and helps reproduce the change if there are any questions.
  • If updating containerd was the goal, why not go get -u github.com/containerd/containerd?
• This seems to be motivated by the presence of a Dependabot alert here. Is it?
  • The vulnerabilities described there don't seem to affect go-containerregistry or its users, since containerd isn't used to pull images. Do you believe this change fixes a real issue, or just accounts for a spurious warning?

In any case, thanks for doing this. I'd just like to understand more the thought process behind it.

[dekkagaijin]

Updated the commit and PR comment.

I agree that go-containerregistry isn't affected, but it costs ~nothing to get rid of the warning and avoid any potential future fire drill(s) as scanners pick it up