fix: replace GKE with teleport EKS cluster

[jessesimpson36]

Which problem does the PR fix?

This is a continuation of the hackathon project which will start replacing some of our CI to use the infra resources. I'm creating the draft PR now since I want to see how much of our integration tests break when trying to introduce this.

What's in this PR?

Checklist

Please make sure to follow our Contributing Guide.

Before opening the PR:

• In the repo's root dir, run make go.update-golden-only.
• There is no other open pull request for the same update/change.
• Tests for charts are added (if needed).
• In-repo documentation are updated (if needed).

After opening the PR:

• Did you sign our CLA (Contributor License Agreement)? It will show once you open the PR.
• Did all checks/tests pass in the PR?

[Langleu]

@jessesimpson36, just a heads up ... not sure the label of janitor is properly added.

From just looking at the changes, I'd say it's not added but I don't know whether anything picks up the env variable in the background that isn't visible to the execeution.

There's a broken namespace for ~ 5 days.

distribution-camunda-pr-2832-intg-alpha-run-13766304287-sfx-451   Active   5d1h

that is hogging quite some resources and none of the resources have the janitor label on it.
(not sure about the namespace, don't have the permissions).

[jessesimpson36]

@Langleu Thanks, I think it will get picked up now.

a4103c7
67c5a18

[jessesimpson36]

I think the load of running the tests with all the versions all at once is too much for the cluster to handle, as everything is pending

[Langleu]

Infra and @bkenez are working on a separate nodepool for those workloads, which would require taints and tolerations to be set. Best to check this out with @bkenez.
The default nodepool, where these are currently ending up, are not big machines + low autoscaling.

[jessesimpson36]

related: https://github.com/camunda/infra-core/pull/9652