chore(deps): update konflux references

[red-hat-konflux]

This PR contains the following updates:

Package	Change
quay.io/konflux-ci/tekton-catalog/task-apply-tags	f44be1b -> 4c2b0a2
quay.io/konflux-ci/tekton-catalog/task-build-image-index	d4c07e2 -> 3411aee
quay.io/konflux-ci/tekton-catalog/task-buildah-remote-oci-ta	0ba240a -> c9eb4f1
quay.io/konflux-ci/tekton-catalog/task-deprecated-image-check	f59175d -> 462baed
quay.io/konflux-ci/tekton-catalog/task-prefetch-dependencies-oci-ta	0503f93 -> 5691652
quay.io/konflux-ci/tekton-catalog/task-sast-shell-check-oci-ta	1f0fcba -> d44336d
quay.io/konflux-ci/tekton-catalog/task-sast-snyk-check-oci-ta	60f2dac -> 8ad28b7
quay.io/konflux-ci/tekton-catalog/task-sast-unicode-check-oci-ta	1833c61 -> e5a8d3e

---

Configuration

📅 Schedule: Branch creation - Between 05:00 AM and 11:59 PM, only on Saturday ( * 5-23 * * 6 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

To execute skipped test pipelines write comment /ok-to-test.

---

Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign msherif1234 for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[openshift-ci]

Hi @red-hat-konflux[bot]. Thanks for your PR.

I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 13.83%. Comparing base (b9d7188) to head (64a7a53).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #412   +/-   ##
=======================================
  Coverage   13.83%   13.83%           
=======================================
  Files          18       18           
  Lines        2277     2277           
=======================================
  Hits          315      315           
  Misses       1938     1938           
  Partials       24       24           

Flag	Coverage Δ
unittests	13.83% <ø> (ø)

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

🚀 New features to boost your workflow:

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

[openshift-ci]

@red-hat-konflux[bot]: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/images	64a7a53	link	true	/test images
ci/prow/integration-tests	64a7a53	link	true	/test integration-tests

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.