chore(ci): Remove trivy - Spark-Operator

[sameerdattav]

Removing trivy action - as instructed by @andreyvelich following kubeflow/katib#2644

[github-actions]

🎉 Welcome to the Kubeflow Spark Operator! 🎉

Thanks for opening your first PR! We're happy to have you as part of our community 🚀

Here's what happens next:

• If you haven't already, please check out our Contributing Guide for repo-specific guidelines and the Kubeflow Contributor Guide for general community standards.
• Our team will review your PR soon!

Join the community:

• Slack: Join our #kubeflow-spark-on-kubernetes Slack channel.

Feel free to ask questions in the comments if you need any help or clarification!
Thanks again for contributing to Kubeflow! 🙏

[Copilot]

Pull request overview

Removes the GitHub Actions workflow that runs scheduled/manual Trivy image vulnerability scans and uploads SARIF results to the GitHub Security tab, aligning this repo’s CI configuration with the referenced upstream instruction.

Changes:

• Deleted the trivy-image-scanning GitHub Actions workflow.
• Removed scheduled (cron) and manual (workflow_dispatch) Trivy scanning execution.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[andreyvelich]

Thanks @sameerdattav!
/lgtm
/approve

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andreyvelich

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 [andreyvelich]

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

[andreyvelich]

/cherry-pick release-2.1
/cherry-pick release-2.2

[google-oss-robot]

@andreyvelich: #2894 failed to apply on top of branch "release-2.1":

Applying: Remove trivy - Spark-Operator
Using index info to reconstruct a base tree...
M	.github/workflows/trivy-image-scanning.yaml
Falling back to patching base and 3-way merge...
CONFLICT (modify/delete): .github/workflows/trivy-image-scanning.yaml deleted in Remove trivy - Spark-Operator and modified in HEAD. Version HEAD of .github/workflows/trivy-image-scanning.yaml left in tree.
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 Remove trivy - Spark-Operator

Details

In response to this:

/cherry-pick release-2.1
/cherry-pick release-2.2

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/test-infra repository.

[andreyvelich]

/cherry-pick release-2.4
/cherry-pick release-2.5

[google-oss-robot]

@andreyvelich: #2894 failed to apply on top of branch "release-2.4":

Applying: Remove trivy - Spark-Operator
Using index info to reconstruct a base tree...
M	.github/workflows/trivy-image-scanning.yaml
Falling back to patching base and 3-way merge...
CONFLICT (modify/delete): .github/workflows/trivy-image-scanning.yaml deleted in Remove trivy - Spark-Operator and modified in HEAD. Version HEAD of .github/workflows/trivy-image-scanning.yaml left in tree.
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 Remove trivy - Spark-Operator

Details

In response to this:

/cherry-pick release-2.4
/cherry-pick release-2.5

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/test-infra repository.

[andreyvelich]

@sameerdattav Please could you manually cherry-pick this commit to the following branches:
release-2.1
release-2.2
release-2.3
release-2.4
release-2.5