Refs. swh/infra/sysadm-environment#5548

This will allow easier testing when ingress are involved in the chart
development.

Refs. swh/infra/sysadm-environment#5344

This also allows to reuse common dependency targets between targets.

This especially allows the preparation steps (secret) work in any machines (some
limitation occurred on some machines because of the file expansion refusing to work).

Refs. swh/infra/sysadm-environment#5344

Actually make it functional for non-default minikube.

Refs. swh/infra/sysadm-environment#5344

This simplifies and unifies the way to pause one's cluster (e.g. either minikube or
kind).

Refs. swh/infra/sysadm-environment#5344

This adds aliases whose named start with local-cluster-*. That way, there is no
discrepancies between the local-cluster-{create,install-deps,remove-deps,...} targets.

Refs. swh/infra/sysadm-environment#5344

Refs. swh/infra/sysadm-environment#5344

This also adds the mean to locally override the gitted local-cluster.yaml
file [1].

[1] Sample:
```
cloudnativePg:
  enabled: true

rabbitmq:
  enabled: true

kafka:
  enabled: true

cassandra:
  enabled: true

elasticsearch:
  enabled: true
```

Refs. swh/infra/sysadm-environment#5344

Refs. swh/infra/sysadm-environment#5344

with the non-gitted Makefile.local

Refs. swh/infra/sysadm-environment#5344

Refs. swh/infra/sysadm-environment#5344

This used to be called *-minikube but as we can use another tool (e.g. kind),
might as well make it agnostic of it.

Refs. swh/infra/sysadm-environment#5344

The local cluster might not be in good shape after a poweroff/restart cycle.
While it's a tad long to use it so the cluster gets back in shape, it's still
possibly faster than an actual delete/create cluster loop.

Refs. swh/infra/sysadm-environment#5344

We cannot declare our own secret, we must let the operator generate it.

Refs. swh/infra/sysadm-environment#5344

And it's now documented in an how to in our documentation site.

Refs. swh/infra/sysadm-environment#5344

So template output is sensible to the local override.

Refs. swh/infra/sysadm-environment#5344

When /minikube-(cc|swh).override.yaml exists, the makefile will override the helm
install command with it. So one can actually enable minikube services through those.

This only impacts the `make cc-minikube` & `make swh-minikube` targets.

Refs. swh/infra/sysadm-environment#5344

Refs. swh/infra/sysadm-environment#5344

So we can test on other local cluster local kube technology (e.g. kind, ...) [1]

[1]
```
make MINIKUBE_CONTEXT=kind-pg swh-minikube
...
```

Refs. swh/infra/sysadm-environment#5311

Refs. swh/infra/sysadm-environment#5311

unless specified otherwise (e.g. `make VERBOSE=1`)

Refs. swh/infra/sysadm-environment#5275

Refs. swh/infra/sysadm-environment#5164

To ease checking the templating is doing ok on various environment/namespace.

so it's idempotent.

Refs. swh/infra/sysadm-environment#4812

As this can be used for the test-staging cluster too.