Update cron schedule for container scan

[ORybak5]

What

Changed the cron schedule for the container scan workflow.

Why

Just to make scans for Docker containers regular but less frequent (4 AM on Monday)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Internal change (non-breaking change with no effect on the functionality affecting end users)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• I have performed a self-review of my code
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have updated the Changelog with details of my change in the UNRELEASED section if this change will affect end users
• A corresponding change has been made to the Mapping Documentation repository

[github-actions]

Images built and published to ECR using a Build Id of PR-1076-23cc01f

[github-actions]

Looks good. No mutations were possible for these changes.
See https://pitest.org

[Copilot]

Pull request overview

This PR is intended to make the container image security scan run less frequently (Mondays at 04:00), but the current diff removes the container scan GitHub Actions workflow entirely, which would stop scheduled (and push-triggered) scanning.

Changes:

• Deletes .github/workflows/container-scan.yml (removing container scan automation), instead of updating its cron schedule.

Comments suppressed due to low confidence (1)

.github/workflows/container-scan.yml:1

• This PR deletes the entire .github/workflows/container-scan.yml workflow rather than updating the cron schedule as described. Unless the intention is to remove container scanning completely, please restore the workflow and change only on.schedule.cron (e.g. 0 4 * * 1). When restoring, also avoid aquasecurity/trivy-action@master (pin to a tagged release or SHA) and note GitHub Actions cron runs in UTC (so confirm “4 AM Monday” is meant in UTC vs local time).

---

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