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

* add keydb as redis replacement

* sort requirements

For some of these, the `ansible_` prefix does not seem to be needed,
but it's the canonical way to do things and it may become required in
newer Ansible versions.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3237

Improve Pantalaimon Support in Draupnir and add Mjolnir support

chore(deps): update gnuxie/draupnir docker tag to v1.87.0

Pin Draupnir Appservice to 1.87.0 instead of Develop & update Draupnir at the same time to the same version.

Appservice Draupnir for All required Develop before the release of 1.87.0 to work at all in the playbook. Now that we have a release to pin to we will return to being pinned to a release. Especially as Draupnir 2.0.0 push is happening now in main. This will mean that Draupnir develop is expected to be much more unstable than usual for a bit so its important that we pin to a stable release. These releases are validated due to having been dogfooded ever since D4A was merged into the playbook.

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