Provision SQS interruption queue for Karpenter

[shreyaabaranwal]

Summary

When Karpenter is enabled, kOps doesn't provision an SQS queue for it, so Karpenter never receives interruption events (spot interruptions, instance state changes, scheduled maintenance, rebalance recommendations). nodeTerminationHandler can't be enabled alongside Karpenter either, since validation blocks that combination, so clusters running Karpenter currently get no interruption handling at all.

• Adds a KarpenterBuilder that provisions an SQS queue plus the EventBridge rules/targets for the four interruption event types, mirroring what's already done for NodeTerminationHandler's queue.
• Passes the queue name into the addon via a new KarpenterQueueName template function, used in both the Helm values (settings.interruptionQueue) and the static manifest (INTERRUPTION_QUEUE env var).
• Adds the SQS permissions Karpenter needs to read from the queue (DeleteMessage, GetQueueUrl, GetQueueAttributes, ReceiveMessage) to AddKarpenterPermissions, added unconditionally since SQS actions don't support resource-level conditions.

Fixes #18016

Test plan

• go build ./...
• gofmt -l . (clean aside from pre-existing vendor files)
• go vet ./pkg/model/... ./cmd/kops/... ./upup/pkg/fi/cloudup/...
• go test ./pkg/model/iam/... ./pkg/model/awsmodel/... ./pkg/model/components/addonmanifests/karpenter/... ./upup/pkg/fi/cloudup/...
• go test ./cmd/kops/... (updated TestKarpenter golden fixtures to include the new SQS queue, EventBridge rules/targets, and IAM policy changes)

[kubernetes-prow]

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

[kubernetes-prow]

Hi @shreyaabaranwal. Thanks for your PR.

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

[shreyaabaranwal]

"Hi @hakman @olemarkus, just checking in on this , happy to make any changes needed.

[shreyaabaranwal]

Hi @hakman @olemarkus, following up again - happy to split this into smaller PRs if that'd make review easier, or address any specific concerns. Let me know what would help move this forward.

[kubernetes-prow]

PR needs rebase.

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.