This also updates validation tasks and documentation, pointing to
variables in the matrix-synapse role which don't currently exist yet
(e.g. `matrix_synapse_container_labels_client_synapse_admin_api_enabled`).

These variables will be added soon, as Traefik labels are added to the
`matrix-synapse` role. At that point, the `matrix-synapse-reverse-proxy-companion` role
will be updated to also use them.

matrix-nginx-proxy is going away and this is one of the features it
offered.

This feature will have no equivalent in our new Traefik-only
setup, although it's possible to implement it manually by using
`matrix_client_element_container_labels_additional_labels`

The spec had gotten updated

This is completely untested.

chore(deps): update halfshot/matrix-hookshot docker tag to v5.1.2

[#3074] Docker tag follows the version properly

This is still very far from usable.

Various bridges and bots are still talking to
`matrix-nginx-proxy` instead of the new `matrix-homeserver-proxy` role.
These services need to be reworked. While reworking them,
various cleanups are being done as well as adding Traefik-labels to
those that need them.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3041

.. because matrix_mautrix_signal_version is used in other places
which do not expect it. For example: `matrix_mautrix_signal_container_image_self_build_branch`

Related to: https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3041

[#3031] Update mautrix-signal to the go version (signalgo merged to signal)

chore(deps): update halfshot/matrix-hookshot docker tag to v5.1.1

chore(deps): update halfshot/matrix-hookshot docker tag to v5.1.0

chore(deps): update dependency etherpad to v1.9.6-0

chore(deps): update halfshot/matrix-hookshot docker tag to v5