See #2529

It's not strictly required yet, but certain versions of Ansible display warnings
if passlib is missing. The non-passlib crypto usage is deprecated, so
passlib will become a requirement in newer Ansible versions. It's only a
matter of time.

* fixes #2586

For backward-compatibility reasons, this playbook uses `matrix` as its
main and default database.

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

The variable was necessary when multiple playbooks could have
potentially tried to manage a shared `devture-traefik.serivce` systemd service
and shared `/devture-traefik` directory.

Since adcc6d9723086f65f1a72, we use our own `/matrix/traefik`
(`matrix-traefik.service`) installation and no conflicts can arise.
It's safe to always enable the role, just like we do with all the other roles.

Completely untested.

This new role also adds native Traefik support and support for other
(non-`amd64`) architectures via self-building.

The new version includes the `passlib` Python module.

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

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

We don't need this anymore. No one should be using matrix-nginx-proxy
anymore.

Change documentation for host bind port when fronting traefik with another reverse proxy

own traefik server option must have the path to the acme.json. Otherwise the service will not start.

Otherwise the public hookshot url will use http and not https

The newly extracted role also has native Traefik support,
so we no longer need to rely on `matrix-nginx-proxy` for
reverse-proxying to Ntfy.

The new role uses port `80` inside the container (not `8080`, like
before), because that's the default assumption of the officially
published container image. Using a custom port (like `8080`), means the
default healthcheck command (which hardcodes port `80`) doesn't work.
Instead of fiddling to override the healthcheck command, we've decided
to stick to the default port instead. This only affects the
inside-the-container port, not any external ports.

The new role also supports adding the network ranges of the container's
multiple additional networks as "exempt hosts". Previously, only one
network's address range was added to "exempt hosts".