Related to https://github.com/devture/exim-relay/pull/11

This bridge doesn't support SQLite anyway, so it's not necessary
to carry around configuration fields and code for migration from SQLite
to Postgres. There's nothing to migrate.

This configuration is supposed to be kept clean and not reference variables defined in other roles.

`group_vars/matrix_servers` redefines these to hook our various roles together.

https://github.com/matrix-org/matrix-appservice-irc/releases/tag/0.30.0

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

Element web/desktop has just been updated to fix some regressions in regard to VoIP.

The Github link is just a redirect to Tulir's own GitLab, so I replaced the self-build link
The docker container repository was rearranged hierarchically (dock.mau.dev/tulir/mautrix-facebook -> dock.mau.dev/mautrix/facebook)
Tagged versions have been made available, thus :latest -> :v0.3.1

As per earlier comment (see from tulir) the sequence has been changed.

Updated settings in template file:
* relay for any user
* user permissions only for HS domain users

Co-authored-by: Jan <31133207+Jaffex@users.noreply.github.com>

Improved setup through template file

Co-authored-by: Jan <31133207+Jaffex@users.noreply.github.com>

Permissions, when set in the template, will be augmented rahter than replaced when using matrix_mautrix_signal_configuration_extension_yaml. Therefore, permissions shall only be set in the defaults/vars.yml or in the HS specific vars.yml file

Per default relay bot functionality is disabled; the bridge user permissions depends on the relay bot, if enabled the base domain users are on level relay, else remain on user;