audit followup: remove k8s-prow iam bindings for jobs that no longer run in k8s-prow

[spiffxp]

Followup to #1534 (comment)

kubernetes/test-infra#19810 migrated some container image promoter jobs to k8s-infra-prow-build-trusted, we don't need k8s-prow to have workload identity bindings for these anymore

This is not intended to outright remove all k8s-prow bindings, some are likely still required for prow.k8s.io to schedule to the k8s-infra prow build clusters

/kind cleanup
/wg k8s-infra
/sig testing
/sig release
/area release-eng
/priority important-longterm
/milestone v1.21

[spiffxp]

/milestone v1.22

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[spiffxp]

/remove-lifecycle stale
Still relevant. Not going to freeze this though

[spiffxp]

/milestone v1.23

[ameukam]

/milestone v1.24

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[ameukam]

/remove-lifecycle stale
/lifecycle frozen
/milestone clear