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

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

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

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

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

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

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

Because the configuration file is now mounted as readonly and maubot tries to update it on start,
we get this warning:
> Failed to create tempfile to write updated config to disk: [Errno 30] Read-only file system: '/config/tmpfa8vcb3y.yaml'

It doesn't seem to cause issues though.

Because the configuration is no longer overwritten on every bot start, each
next Ansible run should no longer overwrite it again and report a
"changed" task.

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

* Make interface hidden behind proxy by default

* Remove expose option and replace with http_bind_port

Reasoning: This is a similar binary trigger but allows to bin not on all interfaces

* Clarify maubot admin purpose

* Remove unnecessary edif

* Extend docs to prevent common misconceptions

* Make http_bind_port singular, do not allow multiple values

* Make optional again

Maubot moanos

This reverts commit 65bfc1396e.

The 1.8.1 image is published now, so we can finally upgrade.

Reasoning: setup_install.yml only runs on --tags=setup-all or on --tags=setup-bot-maubot.

If --tags=setup-nginx-proxy or similar commands are run, setup_install.yml will not run and the nginx configuration will be incomplete.

Fix self-build error image names

Make use of `example.com` more consistent (replace `DOMAIN`) and simplify Caddy 2 config. Remove Caddy 1 config since Caddy 1 is long past EOL.

Explicitly mention that your homeserver's domain is included in telemetry

Update Coturn 4.5.2-r12 -> 4.5.2-r13

Update telemetry documentation to more closely match upstream

**no docker tag yet**, [keep an eye on it](https://hub.docker.com/r/coturn/coturn/tags?page=1&name=4.5.2-r13)

Synapse no longer describes the stats as anonymized since the `server_name` is included.
https://github.com/matrix-org/synapse/pull/13321

This reverts commit 05ccee9f6f.

Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1952

Update Synapse 1.62.0 -> 1.63.0

update Honoroit 0.9.9 -> 0.9.10

Update Redis 7.0.3 -> 7.0.4

Update Hookshot 1.8.0 -> 1.8.1

No docker tag published yet, [keep an eye on it](https://hub.docker.com/r/halfshot/matrix-hookshot/tags?page=1&ordering=last_updated&name=1.8.1)

Ansible lint fixes

This is an attempt to make ansible-lint happy.

Reference: https://ansible-lint.readthedocs.io/en/latest/default_rules/#var-naming

We don't really fix these, but just suppress them,
because they're like that intentionally.

We try to name variables in a way that is consistent with the
configuration key they control. If the upstream component uses
camelCase, we also need to include camelCase in the variable name.

One that doesn't trip up ansible-lint, causing `load-failure` errors.

Reference: https://ansible-lint.readthedocs.io/en/latest/default_rules/#var-spacing

Reference: https://ansible-lint.readthedocs.io/en/latest/default_rules/#no-changed-when

Reference: https://ansible-lint.readthedocs.io/en/latest/default_rules/#git-latest

Our variable naming is not necessarily consistent across roles.
I've tried to follow the naming conventions of each individual role.
All new variables are suffixed with `_version`, but the prefix may be
somewhat different.

Reference: https://ansible-lint.readthedocs.io/en/latest/default_rules/#package-latest