chore(ci): add e2e tests for cloud distros

[noahpb]

Description

Adapts our nightly pipelines (RKE2, EKS and AKS) to run our e2e tests. This PR generally takes our e2e tests that we currently use for k3d and expands them to run against additional k8s distributions and architectures. Notable changes are:

• Adds public load balancers for RKE2 to make Ingress Gateways accessible from github workflows
• Adds a fix for metrics scraping of kube-apiserver components for STIG'd RKE2
• Adds coredns setup tasks for each distro to allow connectivity to *.uds.dev from apps within the cluster
• Adds a new task to ./tasks/test.yaml called uds-core-non-k3d for triggering e2e tests against various distros. This task includes an optional input called EXCLUDED_PACKAGES that allows callers to skip uneccessary tests, such as metrics-server for some distros.
• Allows configuration of the architecture for the ./src/test/package
• Adds a new task to ./tasks/utils.yaml called setup-hosts that configures the local /etc/hosts file to point to *.uds.dev and *.admin.uds.dev domains that are hosted on the cluster that e2e tests are running against.
• Adds timeouts to the curl commands in ./test/jest/network.spec.ts to produce more meaningful error messages when timeouts are occurring during connectivity tests (before these would run indefinitely and the jest timeout would ultimately be reached).
• In ./test/jest/network.spec.ts, changes explicit expect().toBe("503") responses to expect().not.toBe("200") to account for different behavior of cluster CNIs when rejecting traffic due to NetworkPolicy deny rules.

Related Issue

Fixes #729

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Other (security config, docs update, etc)

Steps to Validate

• If this PR introduces new functionality to UDS Core or addresses a bug, please document the steps to test the changes.

Checklist before merging

• Test, docs, adr added or updated as needed
• Contributor Guide followed

[noahpb]

Noting the continue-on-error: true here. EKS VPC CNI permits outbound traffic to the internet for the network tests, despite not having a NetworkPolicy to explicitly allow this. Ignoring failures for now until we decide how to proceed.