so it does not takes forever...

This will perform an exhaustive check that all objects have been replicated
properly using the public API. As such, it is very slow and can possibly
make the execution time of the tests hit the (default) 30mn pytest limit.

This depends on the test kafka dataset to have the TDN topic filled with
a removal notification. Currently, the removed origin for this test is

  https://github.com/SoftwareHeritage/swh-core

Then this will:
- start the notification-watcher service,
- wait for log entries in this service showing the TDN has been received
  from the dedicated kafka topic
(swh.test.mirror-notifications.removal_notification),
- wait for the notification email to be sent,
- check that querying the mirror public API for the removed content
  returns 403,
- check the whole subgraph under the https://pypi.org/project/swh.core/
  origin is still accessible.

also rename ro-storage as storage-public to make it more familiar with
swh-env/docker environment.

These were triggering the docker build linter.

Now swh.core 3.6 has been published, it can be installed properly.

s3 http objstorage use gzip compression.

using the DB_SKIP_INIT env var.

make it consistent to help grafana dashboards

Static assets used by the mirror skin configuration are deployed in
the web service using `docker config` entries; this is not really a practical
solution for a production deployment scheme, but it is simpler for
testing purpose.

and adapt a bit the test config file.

Add a placement contraint for elasticsearch and give vault-db and
scheduler-db their dedicated placement labels.

pushgateway is only useful for specific cases, and accessing the
rabbitmq directly from the host is not really needed.

It seems to speed things a bit.

And scale their respective services directly, without first spawning a
single instance. It slows the test execution significantly (triggering a
kafka rebalance event) without real advantage.

Having a running swh-search service is now de facto mandatory to have a
usable web interface...

This can speed up image rebuilds significantly.

It is now mandatory.

For some reason, the 'python -m swh' stanza does not work any more.

It can have side effects on services not using django like celery
workers, for which this variable triggers a plugin activation.

And update:
- postgres to 16
- pushgateway to 1.8
- redis to 7.2
- rabbitmq to 3.13