`matrix_nginx_proxy_enabled` is usually set to false by users, this is when
the warning should be displayed.

Fixup for d8a19e5bf9

Building mx-puppet-discord appears to have been broken for a while.

Related to:
- https://github.com/matrix-discord/mx-puppet-discord/issues/201
- https://github.com/matrix-discord/mx-puppet-discord/issues/202
- https://github.com/matrix-discord/mx-puppet-discord/issues/203

We'd rather use a fork that is maintained better and by someone who
cares about whether their software works or not, so we'll be using the
Beeper-maintained for from now on.

In the future, we should probably do the same for the Slack bridge
which is also part of the same monorepo
(https://gitlab.com/beeper/mx-puppet-monorepo).

Various roles depend on this. It makes sense to make it part
of the `matrix-base` role.

client-cinny: update to v1.8.0

Riot is now named Element

Related to:

- https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1682
- https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1679

"Federate rooms" switch for mautrix bridges

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

Previously, when matrix-postgres was disabled, we were setting
`matrix_mautrix_twitter_database_engine` to an invalid empty value.

Now, we always hardcode `matrix_mautrix_twitter_database_engine: postgres`,
but set/unset the database hostname and password values instead.

Remove deprecated community options

feat(appservice-discord): add disablePortalBridging bridge option

This allows disabling the automatic portal bridging, meaning bridges
must be manually setup via self-servicing, by setting:

    matrix_appservice_discord_bridge_enableSelfServiceBridging: true

"Community" support

- has been removed from mautrix/facebook in v0.3.3:
  31cac6fb5e

- has been removed from mautrix/signal in v0.2.2:
  1f27a608a6

- will be removed in the next mautrix/instagram release:
  e2ae1ca503

- will be removed in the next mautrix/twitter release:
  3893075265

fix hookshot provisioning url in nginx

This fixes parameters not being passed to the provisioning api

Hello, this PR should fix Hookshot container not receiving API calls with the right path because nginx proxy was stripping the /v1 from it.

Upgrade Hookshot (1.1.0 -> 1.2.0)

all features were actually already silently supported 🎉

upstream changelog: https://github.com/matrix-org/matrix-hookshot/releases/tag/1.2.0

Update hookshot to respect protocol and custom ports

Fix empty body for GET requests in hookshot-bridge

to proxy url params in GET requests

Co-authored-by: Procuria <37988494+Procuria@users.noreply.github.com>

* Add support for obtain ECDSA keys

* Replace matrix_ssl_lets_encrypt_use_ecdsa_keys for matrix_ssl_lets_encrypt_key_type

update hookshot registration.yml

Bump actions/checkout from 2.4.0 to 3

hookshot moved to matrix-org namespace

avoid namespace collisions between webhook bridges

Upgrade Mjolnir (1.3.1 -> 1.3.2)

Bumps [actions/checkout](https://github.com/actions/checkout) from 2.4.0 to 3.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](https://github.com/actions/checkout/compare/v2.4.0...v3)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

Upgrade Element (1.10.5 -> 1.10.6)

Upgrade Element (1.10.4 -> 1.10.5)

GoMatrixHosting v0.7.0