fix(storage): drop imagePullSecrets from OCI auth

[pujitha24]

Changes

When a TaskRun/PipelineRun's ServiceAccount has both imagePullSecrets
and mounted secrets targeting the same OCI registry, the vendored
go-containerregistry keychain consolidates both sets and returns the
first match, which is always the read-only imagePullSecrets
credential. The OCI storage backend (pkg/chains/storage/oci/legacy.go,
still the active auth path wired in pkg/chains/storage/storage.go
despite its "Deprecated" doc-comment on the Backend type) only ever
pushes signed attestations, so resolving a read-only credential makes
the push fail with an auth error even though a push-capable credential
is available in secrets.

This addresses the ServiceAccount-level case described in the issue;
the PodTemplate-level case was already fixed in a prior, separate
change.

Approach

• Bump the vendored github.com/google/go-containerregistry
pkg/authn/kubernetes module to the commit that merged upstream's
  IgnorePullSecrets option
  (feat(kubernetes): allow ignoring pull secrets google/go-containerregistry#2315), which
  lets the keychain skip both the ServiceAccount's imagePullSecrets
  and any explicit pull secrets.
• Set IgnorePullSecrets: true when building the k8schain options used
  by the OCI backend, since this keychain is only ever used to push,
  never to pull.

Validation

• go build ./... passes.
• make test-unit passes for all packages.
• make golangci-lint PKG=./pkg/chains/storage/oci/... reports 0 issues.
• Added TestK8schainOptions_IgnoresImagePullSecrets, confirmed to fail
  if IgnorePullSecrets: true is removed and to pass with the fix,
  asserting the OCI backend's k8schain options are built with
  IgnorePullSecrets set.
• Not run: no live cluster is available in this environment, so the fix
  was not reproduced end-to-end against a real registry. Correctness
  instead relies on the upstream library's own test coverage for
  IgnorePullSecrets plus the added unit test confirming this backend
  threads the option through.

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

• Has Docs included if any changes are user facing
• Has Tests included if any functionality added or changed
• Follows the commit message standard
• Meets the Tekton contributor standards (including
  functionality, content, code)
• Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
• Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

When 'oci' is configured as the storage option for signed artifacts,
the tekton-chains-controller no longer uses the ServiceAccount's
`imagePullSecrets` to authenticate with the target OCI registry when
that ServiceAccount also has push-capable `secrets` for the same
registry.

---

AI assistance: this change was drafted with Claude Code.

Fixes #1336

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 62.03%. Comparing base (b6fe1cf) to head (106f86e).
⚠️ Report is 7 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1883      +/-   ##
==========================================
+ Coverage   61.95%   62.03%   +0.08%     
==========================================
  Files          64       64              
  Lines        4071     4072       +1     
==========================================
+ Hits         2522     2526       +4     
+ Misses       1268     1264       -4     
- Partials      281      282       +1     

Flag	Coverage Δ
unit-tests	62.03% <ø> (+0.08%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[jkhelil]

/retest

[jkhelil]

/approve

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jkhelil

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [jkhelil]

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

[pujitha24]

/assign @wlynch

This has been approved and is green on CI — assigning for an lgtm when you have a moment.

[infernus01]

/lgtm