fix for importing sqllite database

the current version fails the import, because the volume for the media is missing. It still fails if you have the optional shared secret password provider is enabled, so that might need another mount. Commenting out the password provider in the hoimeserver.yaml during the run works as well.

Clarify documentation on port forwarding of Jitsi/TRP behind NAT

Using the older one likely leads to issues like #517.

Fix/mx puppet bridge

Update postgres (12.2 -> 12.3, etc)

enable by default v2 api prefix for ma1sd

We can undo this once https://github.com/ma1uta/ma1sd/issues/44 gets
resolved.

Related to #508 (Github Pull Request).

Jitsi 4548-1 update

Typo STMP -> SMTP

Prevent 404s when Riot tries to retrieve domain-specific config.json

Riot unconditionally asks for a config.${document.domain}.json, c.f.
https://github.com/vector-im/riot-web/blame/develop/src/vector/getconfig.ts#L24

Document how to administer synapse database via tunneled web-frontend

Fixes #494 (Github Issue).

Add note about ask-become-pass

This flag is necessary for Ansible to ask for the sudo password when using the non-root option as documented in the `hosts` file. Otherwise, Ansible errors out with `missing sudo password`.

Fix typo in validation

This is mostly here to guard against problems happening
due to server migration and doing `chown -R matrix:matrix /matrix`.

Normally, the file is owned by `1000:1000`, as expected.

If ownership changes, Dimension could still start, but it will fail the
first time it tries to write to the database. Explicitly chowning
before startup guards against this.

Related to #485 and #486 (Github Pull Requests).
Also related to ccc7aaf0ce.

Dimension runs as the `node` user in the container (`1000:1000`).
It doesn't seem like we have a way around it. Thus, its configuration
must also be readable by that user (or group, in this case).

We don't really need to fail in such a spectactular way,
but it's probably good to do. It will only happen for people
who are defining their own user/group id, which is rare.

It seems like a good idea to tell them that this doesn't work
as they expect anymore and to ask them to remove these variables,
which otherwise give them a fake sense of hope.

Related to #486 (Github Pull Request).

Related to #485 (Github Pull Request).

Remove default UID/GID