It must be initialized manually for the moment

Related to swh/infra/sysadm-environment#5391

It's mostly probable that local clusters don't have a prometheus
operator deployed.

Instead of only the nested-level volumeClaimTemplate.

Refs. swh/infra/sysadm-environment#5344

Refs. swh/infra/sysadm-environment#5344

Refs. swh/infra/sysadm-environment#5344

Refs. swh/infra/sysadm-environment#5344

And place it in the right position in the K8ssandraCluster kind.

Refs. swh/infra/sysadm-environment#5344

Refs. swh/infra/sysadm-environment#5344

Refs. swh/infra/sysadm-environment#5344

Refs. swh/infra/sysadm-environment#5344

```
bash-4.4# curl -s ${SERVER}/_cat/health\?v
epoch      timestamp cluster status node.total node.data shards pri relo init unassign pending_tasks max_task_wait_time active_shards_percent
1720616631 13:03:51  search  green           3         3      4   2    0    0        0             0                  -                100.0%

```

Refs. swh/infra/sysadm-environment#5344

So we have a similar behavior as our current elasticsearch server (for
internal communication).

Refs. swh/infra/sysadm-environment#5344

For our local cluster test purposes.

Refs. swh/infra/sysadm-environment#5344

Refs. swh/infra/sysadm-environment#5344

Refs. swh/infra/sysadm-environment#5344

Refs. swh/infra/sysadm-environment#5344

Refs. swh/infra/sysadm-environment#5344

Unfortunately, the current strimzi operator refuses to use partially the authentication.
Once activated, this must be the case for all entities using the kafka topics (be it the
storage or the replayers).

We are not using the authentication part for the storage part so let's disable it for
now.

The storage replayer template got adapted to allow the anonymous mode use.

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 enable storage replayers to start replay data from kafka topics (populated by the
cassandra storage) inside a storage postgresql instance (to serve as read-only backend).

Refs. swh/infra/sysadm-environment#5344

Refs. swh/infra/sysadm-environment#5344

Refs. swh/infra/sysadm-environment#5344

Refs. swh/infra/sysadm-environment#5344

Refs. swh/infra/sysadm-environment#5344

Refs. swh/infra/sysadm-environment#5344

So when toggled, it just starts ok.

Refs. swh/infra/sysadm-environment#5344

It's common between environments.

Refs. swh/infra/sysadm-environment#5344

Refs. swh/infra/sysadm-environment#5344

Refs. swh/infra/sysadm-environment#5344

The initialization and migration is already dealt with in that template.

Refs. swh/infra/sysadm-environment#5344

Refs. swh/infra/sysadm-environment#5344

Refs. swh/infra/sysadm-environment#5344

Refs. swh/infra/sysadm-environment#5344

Refs. swh/infra/sysadm-environment#5344

cc: cluster-components

Refs. swh/infra/sysadm-environment#5344

Refs. swh/infra/sysadm-environment#5344

It was not supposed to be committed on.

Refs. swh/infra/sysadm-environment#5344

Refs. swh/infra/sysadm-environment#5311

Refs. swh/infra/sysadm-environment#5275