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

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

Hopefully fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1518

Discussed here: https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1510

This is the equivalent of b1b4ba501f for the matrix-dendrite role.

This brings matrix-dendrite.service in line with all the other services.

We're trying to move away from implementation-specific variables,
hoping for a clean (implementation-neutral) examples/vars.yml file.

Doing this seems more reasonable and simpler.

Also get rid of `--tags=update-user-password` in the
`matrix-dendrite` role, as what we had doesn't work.

We may be able to do it with some Ansible helper or something else.
For now, we'll omit this feature.

We also need to fix `--tags=register-user`. This tag is currently
defined in both the `matrix-synapse` and `matrix-dendrite` roles.

All the `matrix_s3_*` stuff happens in the `matrix-synapse` role.

If we are to have such S3 support for Dendrite, we should probably
extract it out of the `matrix-synapse` role (into a `matrix-s3` role or
`matrix-goofys`, etc.) and wire `matrix-dendrite` accordingly.

This may or may not be done in the future though. For now, I'm
cleaning things up in the `matrix-dendrite` role.

Seems like Dendrite encourages serving both the Client and Federation
API at the same port.

Coming from Synapse and how things are done there, we have separate
ports. Using separate ports probably makes matrix-corporal (etc.)
integration easier, so separating the APIs by default probably makes
sense.

Since 025a5ab5e5f6bdb3, we do a similar check in matrix-base.

The goal is to have a single variable which tells us which homeserver
software is in use. Much simpler than having if/elif/elif checks for
variables like (`matrix_synapse_enabled` and `matrix_dendrite_enabled`, etc.)
everywhere.

This brings dendrite.yaml up to date and cleans things up a bit.

We refrain from logging to files for all components,
because we rely on systemd-journald anyway.

Discussed in https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1514

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

ExecStopPost should allow us to clean up (docker kill + docker rm)
even if the ExecStart (docker run ..) command failed, and not just after
a graceful service stop was initiated.

Source: https://www.freedesktop.org/software/systemd/man/systemd.service.html#ExecStopPost=