Bridge mautrix signal and mautrix whatsapp encryption

Details here: https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_6.html#id36

Basically:

```yaml
- name: Prior to 2.13
  debug:
    msg: '[1] + {{ [2] }}'

- name: 2.13 and forward
  debug:
    msg: '{{ [1] + [2] }}'
```

Interestingly, we had been using the new/safe syntax in lofs of places.

We were using the broken one in many others though. Hopefully all
instances were fixed by this patch.

Update Synapse v1.59.0 -> v.1.59.1

This new version should be buildable on arm64.

See: https://github.com/matrix-org/matrix-hookshot/releases/tag/1.7.0

There's still no prebuild arm64 image, so we continue relying on
self-building there.

Update Postgres (CVE-2022-1552 + last 9.x update)

Update mautrix-whatsapp v0.3.1 -> v0.4.0

Upgrade Heisenbridge (1.12.0 -> 1.13.0)

Related to https://gitlab.com/mx-puppet/discord/mx-puppet-discord/-/issues/117

Looks like the bridge is too quick to start and fails to initialize
itself by connecting to Synapse. It's mostly observed after a system
reboot, because Synapse (and everything else) is slower to start.

Once mx-puppet-discord fails to initialize itself, a "No relay found"
error will be observed any time you try to relay a Matrix message to
Discord. Relaying messages in the other direction (Discord to Matrix)
also fails.

With this workaround (longer delay on mx-puppet-discord startup), I
observe mx-puppet-discord working well, even after a full reboot.
Of course, a proper fix is preferable, instead of delaying by a magic
number of seconds.

CVE: https://security-tracker.debian.org/tracker/CVE-2022-1552
Source: https://www.postgresql.org/about/news/postgresql-143-137-1211-1116-and-1021-released-2449/
Postgres 9.6 upgrade (**not a CVE fix, 9.x still vulnerable**): https://www.postgresql.org/docs/release/9.6.24/

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

Change back to working original mx-puppet-slack

Update Element self build repo URL

Document `git` as a potential prereq

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

It forwards to the correct place but might as well just update it to the current URL.

Update Cinny v2.0.2 -> v2.0.3

Now that v0.1.1 is out, which depends on the functional matrix-slack-parser
it works again.

Update Cinny v2.0.1 -> v2.0.2

Update Cinny v2.0.0 -> v2.0.1

Update configuring-playbook-bridge-hookshot.md

fix Hookshot instructions link

Suggested fix to docs for reverse proxy for well-known file

Bump Slack Appservice to 1.11.0

matrix-bot-buscarron v1.1.0

Update configuring-playbook-bridge-hookshot.md

Update Element 1.10.11 -> 1.10.12

Update cinny v1.8.2 -> v2.0.0

This reverts commit fcfd00bcb4.

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

Reverts https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1809

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

Change back to original mx-puppet-slack

Closes: #1808