Use OIDC for e2e tests instead of repository credentials

[turkenh]

What problem are you facing?

Today, e2e workflow expects cloud credentials to be defined and provided as repository secrets. Usage of hardcoded credentials i not optimal.

How could Upbound help solve your problem?

Github actions also supports OIDC with cloud providers as described here. This would have the following benefits:

• No cloud secrets: You won't need to duplicate your cloud credentials as long-lived GitHub secrets. Instead, you can configure the OIDC trust on your cloud provider, and then update your workflows to request a short-lived access token from the cloud provider through OIDC.
• Authentication and authorization management: You have more granular control over how workflows can use credentials, using your cloud provider's authentication (authN) and authorization (authZ) tools to control access to cloud resources.
• Rotating credentials: With OIDC, your cloud provider issues a short-lived access token that is only valid for a single job, and then automatically expires.