chore(deps): update konflux references

[red-hat-konflux-kflux-prd-rh02]

This PR contains the following updates:

Package	Change	Notes
quay.io/konflux-ci/tekton-catalog/task-apply-tags	f44be1b -> e4017ec
quay.io/konflux-ci/tekton-catalog/task-build-image-index	0.1 -> 0.2	⚠️migration⚠️
quay.io/konflux-ci/tekton-catalog/task-buildah-remote-oci-ta	0.6 -> 0.7	⚠️migration⚠️
quay.io/konflux-ci/tekton-catalog/task-clair-scan	8ec7d7b -> ee558db
quay.io/konflux-ci/tekton-catalog/task-ecosystem-cert-preflight-checks	9568c51 -> 04f7559
quay.io/konflux-ci/tekton-catalog/task-git-clone-oci-ta	3dc39ea -> 0a89e1a
quay.io/konflux-ci/tekton-catalog/task-init	3ca52e1 -> 75b88ee
quay.io/konflux-ci/tekton-catalog/task-prefetch-dependencies-oci-ta	0503f93 -> 3fa0204
quay.io/konflux-ci/tekton-catalog/task-push-dockerfile-oci-ta	13633d5 -> 08bba4a
quay.io/konflux-ci/tekton-catalog/task-source-build-oci-ta	282cb5a -> 4abb2db

---

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.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[openshift-ci]

Hi @red-hat-konflux-kflux-prd-rh02[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.

[tisnik]

LGTM