Bump go-containerregistry dependency

[dprotaso]

User reported k8schain was failing with serving but not with the latest version of go-containerregistry.

See: https://cloud-native.slack.com/archives/C04LGHDR9K7/p1738857680364749

This bumps the ggcr dependency. They can test tomorrow when a nightly comes out - afterwards we can cherry pick changes.

Bump go-containerregistry to address issues with tag to digest resolution on EKS

[dprotaso]

/assign @skonto

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 80.78%. Comparing base (a9c5467) to head (021a9fc).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #15754      +/-   ##
==========================================
- Coverage   80.81%   80.78%   -0.04%     
==========================================
  Files         222      222              
  Lines       18075    18075              
==========================================
- Hits        14607    14601       -6     
- Misses       3098     3101       +3     
- Partials      370      373       +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[skonto]

/lgtm
/approve

[knative-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dprotaso, skonto

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 [dprotaso,skonto]

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

[dprotaso]

capturing linter error here - #15755 it is a know issue

/override "style / Golang / Lint"

[knative-prow]

@dprotaso: Overrode contexts on behalf of dprotaso: style / Golang / Lint

In response to this:

capturing linter error here - #15755 it is a know issue

/override "style / Golang / Lint"

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.