chore(deps): update dock.mau.dev/mautrix/gmessages docker tag to v0.4.0

chore(deps): update dock.mau.dev/mautrix/whatsapp docker tag to v0.10.7

exim-relay: fix dkim permissions, fix sender address

Resolve Synology DSM 7.2 Docker Command Issue

This also removes the condition that made it use `latest` when
self-building is enabled.

v0.1.4 is expected to build correctly now, given that this issue is fixed:
https://github.com/matrix-org/rust-synapse-compress-state/issues/134

chore(deps): update dependency prometheus to v2.51.2-0

chore(deps): update dependency grafana to v10.4.2-0

chore(deps): update matrixdotorg/sygnal docker tag to v0.14.1

chore(deps): update matrixdotorg/dendrite-monolith docker tag to v0.13.7

I believe this wiring had gotten lost at some point before.

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

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

Meta messenger documentation clarification

* Add link to database migration documentation.
* Correct configuration snippet to dict instead of str

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

chore(deps): update ghcr.io/element-hq/synapse docker tag to v1.104.0

add matrix_synapse_redis_dbid var

This new version makes the mail spool persistent, so that exim can be
restarted without losing queued messages.

chore(deps): update dependency backup_borg to v1.2.8-1.8.9-0

Ref: 0e05a332db (commitcomment-140240527)

Only `amd64` and `arm64` actually work.

The KeyDB role includes a validation task and will complain about
unsupported architectures (like `arm32`).

`arm32` users can stick to Redis for now (`keydb_enabled: false` + `redis_enabled: true`) until:
- the KeyDB role starts supporting self-building.. although building such large
  projects on weak CPUs is probably impractical
- a prebuilt arm32 image is made available by other means

This reverts commit 9c01d875f3.

This is very confusing and messy.. but it's documented.
`ansible_become_*` variables actually take priority and override all `become_*`
variables set at the task level.

As such, using `ansible_become=true ansible_become_user=root` in
`inventory/hosts` causes issues because tasks that specify
`become: OTHER_USER` will be forced to run as `root` due to
`ansible_become_user`.

chore(deps): update dependency redis to v7.2.4-0