Update the e2e workflow to use the Makefile targets to setup kind cluster and run tests

Currently we are using the old way of creating the kind cluster i.e.
```yaml
- name: Create k8s Kind Cluster
uses: engineerd/setup-kind@v0.5.0
with:
version: "v0.9.0"
name: orkestra
wait: 10s
config: .kind-cluster.yaml
- name: Deploy
run: |
curl https://baltocdn.com/helm/signing.asc | sudo apt-key add -
sudo apt-get install apt-transport-https --yes
echo "deb https://baltocdn.com/helm/stable/debian/ all main" | sudo tee /etc/apt/sources.list.d/helm-stable-debian.list
curl -s "https://raw.githubusercontent.com/kubernetes-sigs/kustomize/master/hack/install_kustomize.sh" | bash
sudo apt-get update
sudo apt-get install helm
kind export kubeconfig --name orkestra
helm install orkestra chart/orkestra --wait --atomic -n orkestra --create-namespace --values chart/orkestra/values-ci.yaml
- name: Verify Deployment
run: |
curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl"
chmod +x kubectl
sudo mv kubectl /usr/local/bin
kubectl cluster-info
echo "current-context:" $(kubectl config current-context)
```

We should switch over to the `Makefile` targets that we use in our development workflow instead to mimic what contributors will use for local testing, i.e

```terminal
make clean
make dev
make test
```