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.

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

Clarify reverse-proxying of well-known files with Caddy2

Change back to original mx-puppet-discord

Add hookshot feeds config support

Upgrade Hookshot (1.5.0 -> 1.6.1)

Closes: #1801

These endpoints should not be proxied to a generic Synapse worker
without other preparation (setting up stream writers, sending traffic
to a specific stream writer, etc.).

Disabling them for now. In the future, we'd like to fix up our awk
script to disable them automatically.

This is a fix up for 058fedff91