Update ci teardown to cluster init

[leonlnj]

Summary

Refactor existing Turing CI workflow, to remove tear down of cluster and do it as an e2e test part of cluster-init workflow.

Modification

.github/actions/cluster-init/action.yaml - New github action to be called by both Turing and cluster-init workflow to init the cluster. It will contain inputs to optionally build an image or to use an built jar.
The steps involved are:

1. Setup k3d cluster
2. (Optional) Build and save Cluster-Init Image
3. Push image to local registry
4. Install cluster

.github/workflows/cluster-init.yaml - Updated to include an e2e test.
Steps

1. Trigger cluster-init github action
2. Deploy an knative service for smoke test
3. Tear down infra

.github/workflows/turing.yaml - Extracted installation of cluster as github action and to call the action instead. Removed tearing down of cluster.

[romanwozniak]

@leonlnj I understand that this is a draft PR, but in case you haven't considered it yet, then my early feedback would be to share common cluster setup steps between cluster-init/test-e2e and turing/test-e2e workflows with a custom Github Action. This action can encapsulate repeated steps of starting up k3d cluster, adding cluster-init Docker image into a K3d's local image registry, and cluster provisioning with the cluster-init job.

gojek/turing already contains one custom action here: https://github.com/gojek/turing/blob/main/.github/actions/release-rules/action.yaml

[leonlnj]

ah thanks, i was still looking around on how to extract common code, that helps!

[romanwozniak]

Added a suggestion on how to make cluster-init workflow aligned with the main Turing CI workflow (to structure it as build -> test-e2e -> publish). The rest looks good!