v0.7.0

• When we push changes to the branch, go-git logs a message by default : it contains link to create PR against the upstream repository (Obmondo's kubeaid-config). I need to take a look at whether we can disable this or not.

• At the end of the cluster setup process, print out a help text for the user : containing command which the user can just copy paste and then visit localhost:8080 to access the ArgoCD dashboard.

• Have a flag, which can be used to make the script push changes directly to the main branch instead of going through the PR flow (this should be used while testing only).

• Have a --skip-monitoring-setup flag, to skip KubePrometheus installation.

• Use a dedicated K3D container image registry

• During cluster setup phase, install ArgoCD and Sealed Secrets using KubeAid's charts and not direct upstream's charts

• ArgoCD App file name format changed from*.app.yaml to *.yaml.
  Helm chart values file name format changed from*.values.yaml to values-*.yaml.

• --debug flag works.

• time slog attribute will be present only in debug mode.

• Fix CI build failure by doing :

	// We need this, otherwise Github Actions CI run will fail with this error :
	// https://github.com/Obmondo/kubeaid-bootstrap-script/actions/runs/14102269130/job/39500847660#step:6:5993.
	// REFER : https://github.com/argoproj/argo-cd/issues/22007.
	github.com/cyphar/filepath-securejoin => github.com/cyphar/filepath-securejoin v0.3.6

• colored logger

Azure specific work done :

• Azure Workload Identity + ClusterAPI setup

  A small task is still remaining. I need to change a command, so az login can be done non-interactively.