fix: sanitize wildcard hostnames in certificate resource ID for ACM tags

[Dasmat13]

Description

This pull request resolves a bug where ACM certificate requests fail for Ingresses with wildcard hostnames due to invalid character restrictions in AWS tag values (#4836).

The certificate resourceID embeds the DomainName and is used as the ingress.k8s.aws/resource tracking tag value. However, AWS ACM API validation rejects * in tag values ([\p{L}\p{Z}\p{N}_.:/=+\-@]*), causing RequestCertificate calls to fail with a 400 ValidationException for wildcard host configurations.

This change sanitizes the resourceID by replacing the * character with "wildcard" in buildCertificateResourceID(). The actual DomainName and SubjectAlternativeNames sent to ACM remain unchanged, ensuring certificate coverage is unaffected while preventing the validation failure.

Testing

• Added unit tests covering all wildcard/non-wildcard/multi-wildcard cases for buildCertificateResourceID().
• Added an E2E test case in test/e2e/ingress/acm_ingress_test.go exercising wildcard-host Ingress certificate validation.
• All unit tests (go test ./pkg/...) pass successfully.

[kubernetes-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Dasmat13
Once this PR has been reviewed and has the lgtm label, please assign zac-nixon 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 @Dasmat13. 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.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

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.