Gmessage bridge: Remove file logging, and add existing log level variable to config

* Adjust to new mrb docker versioning

* Stabilze authentication

* fix lint

* Move & document mrb password usage

* Add clean cache role

* Document clean cache

* Fix lint

* Update CHANGELOG.md

* Automate access tokens

* Improve changelog

* Make use of mrb's function to fetch API tokens

* Adjust changelog

* Use ansible.builtin.file to clear directory

* Fix typo

---------

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

Shortening the salt

The salts need to be shorter than 16 chars

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

* intial commit

* changed

* Reorderd

* merge old changes

* added changes to matrix_servers

* Remove duplicate discord

* Update main.yml

* added google message to configuring-playbook.md

* Changed docs to add new changes

* Changed bug?

* Removed problem j2 values

* Rename a service files

* change how password hash string

* Changed port number

* Change how the local part works

* Revert "Merge pull request #8 from shreyasajj/wsproxy"

This reverts commit bb1b8fc67ca39f63ca77e70077be99cb2b32c4de, reversing
changes made to cce6ba5f9d.

---------

Co-authored-by: Shreyas Ajjarapu <github.tzarina@aleeas.com>

add global bridges relay mode switch

This is more secure as most setups do not expose admin API endpoints to the outside world.

Update element 1.11.35 -> 1.11.36

As mentioned in https://github.com/matrix-org/sliding-sync/issues/31#issuecomment-1640321110
images are available for arm64 already.

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

Update whatsapp version

Added matrix-media-repo role

Making the group match the Ansible task tags allows people to do `just install-service matrix-media-repo` and have that trigger both `--tags=matrix-media-repo` and also restart just that single group (`matrix-media-repo`).

Update mautrix-discord 0.5.0 -> 0.6.0

Upgrade sliding-sync (v0.99.3 -> v0.99.4)

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

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

Explain the option of manually defining your public IP in the documentation for Coturn

Explicitly refer users to the relevant roles file so people know where to find the additional configuration options.

I was very surprised by the fact that a rather important configuration for coturn was "hidden" in the Hosts file, but not mentioned here. 

Therefore my suggestion is to explicitly mention it here, as I believe that is that natural for people to look.