refactor: all unit/e2e tests to Golang

[tommartensen]

• Refactors the remaining BATS tests to Golang and removes the parts of CI that run BATS tests.

Required changes:

• infractl create --rhacs flag is now always exposed, this is required because os.Args can't be modified to include the flag if we run go test.
• refactored the current working environment and naming logic for clusters in infractl create. We need to be able to mock the working environment in e2e tests and it was all a bit hard to read
• infractl flavor list --json now returns the flavor availability as a string, not enum int (ie alpha instead of 0). This improves usability.
• WorkflowTemplate2Flavor now returns a flavor and a list of validation errors. The behaviour of logging and ignoring validation errors during service startup remains the same, but I implemented unit tests that check the errors. WorkflowTemplates are now removed, because they are unused (except tests - also refactored to just Workflows)
• Reduced the lifespan and create/delete delays in e2e tests to make them a bit quicker.

Also:

• experimented with t.Parallel() - that was too unstable for my liking. Can be revisited later.

[rhacs-bot]

A single node development cluster (infra-pr-1524) was allocated in production infra for this PR.

CI will attempt to deploy quay.io/rhacs-eng/infra-server:0.11.0-38-gc6159cf9c3 to it.

🔌 You can connect to this cluster with:

gcloud container clusters get-credentials infra-pr-1524 --zone us-central1-a --project acs-team-temp-dev

🛠️ And pull infractl from the deployed dev infra-server with:

nohup kubectl -n infra port-forward svc/infra-server-service 8443:8443 &
make pull-infractl-from-dev-server

🚲 You can then use the dev infra instance e.g.:

bin/infractl -k -e localhost:8443 whoami

⚠️ Any clusters that you start using your dev infra instance should have a lifespan shorter then the development cluster instance. Otherwise they will not be destroyed when the dev infra instance ceases to exist when the development cluster is deleted. ⚠️

Further Development

☕ If you make changes, you can commit and push and CI will take care of updating the development cluster.

🚀 If you only modify configuration (chart/infra-server/configuration) or templates (chart/infra-server/{static,templates}), you can get a faster update with:

make helm-deploy

Logs

Logs for the development infra depending on your @redhat.com authuser:

• authuser=0
• authuser=1
• authuser=2

Or:

kubectl -n infra logs -l app=infra-server --tail=1 -f

[davdhacs]

+1💥!