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

Feature/signal config

Upgrade Element (1.8.0 -> 1.8.1)

Mautrix-Facebook repo location update, pin v0.3.1

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

Pin Heisenbridge to 1.0.0

docker-ce is now available for Debian Bullseye

comment to trigger update

See merge request GoMatrixHosting/matrix-docker-ansible-deploy!3

revert to previous version

See merge request GoMatrixHosting/matrix-docker-ansible-deploy!2

GoMatrixHosting v0.5.7

Testing v0.5.8

See merge request GoMatrixHosting/matrix-docker-ansible-deploy!1

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

Improvement of documentation

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

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>

Document how to enable relay functionality in a room

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;

Enable / disable relay bot functionality as configuratoin paramter; set bridge permissions for base domain users to user level