Bump c/storage to v1.59.0, c/image to v5.36.0

[TomSweeneyRedHat]

Possible replacement for #2476. I'm not sure if I messed something up when trying to merge in #2478 there, so I thought I'd create this PR to see if I messed something up there when doing the merge/vendor.

If this passes the lint tests, I'll add the common bumps, and I'll kill #2476

Summary by Sourcery

Upgrade primary and indirect Go dependencies to the latest compatible versions

Enhancements:

• Bump github.com/containers/image/v5 to v5.36.0
• Bump github.com/containers/storage to v1.59.0
• Update various indirect modules (e.g., mergo, hcsshim, docker/docker, go-logr, sqlite3, sigstore, opentelemetry, grpc) to newer versions

Build:

• Regenerate go.mod and go.sum to reflect updated dependency versions

[sourcery-ai]

Reviewer's Guide

Upgrade primary container modules (containers/image and containers/storage) to the latest releases and sync all indirect dependencies via go mod tidy, updating go.sum accordingly.

File-Level Changes

Change	Details	Files
Bump primary dependencies versions	containers/image v5.35.0 → v5.36.0 containers/storage v1.58.0 → v1.59.0	go.mod
Refresh indirect modules and checksums	Upgrade various indirect modules (mergo, hcsshim, docker, logr, sqlite3, sigstore, go-patricia, mpb, OpenTelemetry, gRPC) Run go mod tidy and regenerate go.sum	go.mod go.sum

Possibly linked issues

• fix(deps): update module github.com/containers/storage to v1.59.0 #2473: PR updates github.com/containers/storage to v1.59.0, directly addressing the dependency update in the issue.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @TomSweeneyRedHat - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sourcery-ai[bot], TomSweeneyRedHat

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [TomSweeneyRedHat]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[TomSweeneyRedHat]

Don't merge! I was working on a few small lint errors when the prior PR was closed. I'll create a new PR to fix those up.

[TomSweeneyRedHat]

Closing. Versions and lint issues will be taken care of elsewhere.