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;

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

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1225

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

See https://github.com/mautrix/whatsapp/releases/tag/v0.1.8

Regression since 421f85defa

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1171

All of `setup_install.yml` only runs if `matrix_bot_matrix_reminder_bot_enabled`,
so it's not necessary to add that condition once again.

We'd rather not suppress pull errors or run self-build tasks if pulling fails.

* root path for the base domain

* Fix path when running in a container

Co-authored-by: Slavi Pantaleev <slavi@devture.com>

Fixes an issue related to https://github.com/anoadragon453/matrix-reminder-bot/issues/86