✨ feat: add automated AMI detection workflow

[krrish175-byte]

What type of PR is this?

/kind feature

What this PR does / why we need it:

This PR introduces an automated workflow to detect new stable Kubernetes releases and trigger AMI builds for them. This replaces the manual process of constantly watching for new releases and manually triggering builds.

Key features:

• New Workflow: .github/workflows/auto-ami-detection.yml runs every 6 hours.
• State Tracking: Uses .github/processed-k8s-versions.json to prevent duplicate builds for the same version.
• Safety:
  • Splits detection and triggering into separate jobs.
  • Requires manual approval via the ami-production GitHub Environment before triggering expensive builds.
  • Uses concurrency to prevent overlapping runs.
• Cost Optimization: Default configuration triggers builds for a reduced set of critical regions (us-east-1, us-west-2, eu-west-1, ap-southeast-1) to verify functionality before expanding.
• Documentation: Updated docs/book/src/development/amis.md with details on the new automation.

Which issue(s) this PR fixes:
Fixes #5837

Special notes for your reviewer:

• This workflow requires a GitHub Environment named ami-production to be configured in the repository settings with "Required reviewers" enabled.
• The workflow has contents: write permissions to update the tracking file and actions: write permissions to trigger the build workflow.

Checklist:

• squashed commits
• includes documentation
• includes emoji in title
• adds unit tests
• adds or updates e2e tests

Release note:

Action Required: Configure a GitHub Environment named `ami-production` with required reviewers to enable manual approval for the new automated AMI build trigger.
✨ Added automated workflow for detecting new Kubernetes releases and triggering AMI builds.

[k8s-ci-robot]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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.

[k8s-ci-robot]

[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 fabriziopandini 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

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: krrish175-byte / name: Krrish Biswas (7204824)

[k8s-ci-robot]

Welcome @krrish175-byte!

It looks like this is your first PR to kubernetes-sigs/cluster-api-provider-aws 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/cluster-api-provider-aws has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @krrish175-byte. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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.