Migrate azure workload (indexer, cooker) to aks (kubernetes in azure)

We should at first consider the pros/cons of deploying in our infra vs the azure infra.

The current maintenance of the indexer and cooker in the old infra is tedious. It also prevents us from dropping the debian packages.

While the maintenance of the pods in kubernetes will be the same as what we now do in staging (and tend for production).

1. our charts are ready for indexers & cookers workers, indexer storage & vault rpc services.
2. We already have aks clusters running (for the prod/staging gitlab).
3. The monitoring is already ready for pods so we'd see what happens
4. We can craft better alerts when something is off (with the new monitoring stack)

status:

• #5211 (closed): vault workload
• indexer workload (partially)

[1] swh/infra/ci-cd/swh-charts!167 (closed)