🐛 fix: backwards compatibility for AWS service endpoint resolution

[tthvo]

What type of PR is this?
/kind bug

What this PR does / why we need it:

In AWS SDKv1, each service exports a constant EndpointsID to look up the custom service endpoint, for example, see ref [0]. In AWS SDKv2, these contants are no longer available. Thus, for backwards compatibility, we copy those constants from the SDKv1 and map them to the corresponding ServiceID in SDK v2.

Additionally, in AWS SDKv1, elb and elbv2 uses the same identifier (i.e. same EndpointsID), thus the same custom endpoint [1] [2]. For backwards compatibility, if elbv2 endpoint is undefined, elbv2 endpoint resolver should fall back to elb endpoint if any.

This also fixes the bug where CAPA does not recognize services that define its serviceID with more than 1 word due to the incorrect assumption endpoints.go#L90-L94). The services are:

• Elastic Load Balancing
• Elastic Load Balancing v2
• Resource Groups Tagging API
• EventBridge
• Secrets Manager

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #5670

Special notes for your reviewer:

Checklist:

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

Release note:

ensure custom service endpoints for supported AWS services are properly selected by
both AWS SDKv2 and SDKv1 service ID (for backwards compatibility) 

[k8s-ci-robot]

Hi @tthvo. 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.

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.

[damdo]

Cc. @punkwalker

[damdo]

/ok-to-test

[damdo]

Thanks a lot for this

/lgtm

/assign @richardcase @nrb

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: db425f99a2ecae7ffe35f04d4036734139e1fb76

[damdo]

/cherry-pick release-2.9

[k8s-infra-cherrypick-robot]

@damdo: once the present PR merges, I will cherry-pick it on top of release-2.9 in a new PR and assign it to you.

In response to this:

/cherry-pick release-2.9

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.

[nrb]

/approve
/hold
until the question about endpoint coverage is answered.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nrb

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [nrb]

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

[nrb]

/unhold

[k8s-infra-cherrypick-robot]

@damdo: new pull request created: #5682

In response to this:

/cherry-pick release-2.9

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.