* Fix bug that prevented user with external nginx from launch

The backslash was missing and prevented users from starting the bot

* Add necessary config for ext nginx to docs

* Add automatic config for ext nginx, adjust docs

* Remove unneeded and possibly puzzeling documentation

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

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

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

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

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

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

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

Because the configuration file is now mounted as readonly and maubot tries to update it on start,
we get this warning:
> Failed to create tempfile to write updated config to disk: [Errno 30] Read-only file system: '/config/tmpfa8vcb3y.yaml'

It doesn't seem to cause issues though.

Because the configuration is no longer overwritten on every bot start, each
next Ansible run should no longer overwrite it again and report a
"changed" task.

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

* Make interface hidden behind proxy by default

* Remove expose option and replace with http_bind_port

Reasoning: This is a similar binary trigger but allows to bin not on all interfaces

* Clarify maubot admin purpose

* Remove unnecessary edif

* Extend docs to prevent common misconceptions

* Make http_bind_port singular, do not allow multiple values

* Make optional again

Reasoning: setup_install.yml only runs on --tags=setup-all or on --tags=setup-bot-maubot.

If --tags=setup-nginx-proxy or similar commands are run, setup_install.yml will not run and the nginx configuration will be incomplete.

This shall indicate that the public url of maubot is here configured the same as matrix_server_fqn_matrix but this must not be the case.
In the config I used the matrix fqnd directly as this part of the config is directly bound to the homeserver we want to connect to (but can not use the internal)

The /data is hardcoded in the container

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

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

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