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

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

The latest tagged release (v0.1.3) does not pin any versions in its
Dockerfile and as such fails to build right now.

The `main` branch of rust-synapse-compress-state has already addressed
this and is buildable, but there's no tagged release yet.

Reported here: https://github.com/matrix-org/rust-synapse-compress-state/issues/134

update mautrix-signal

chore(deps): update vectorim/element-web docker tag to v1.11.53

The spec had gotten updated

chore(deps): update halfshot/matrix-hookshot docker tag to v5.1.2

[#3074] Docker tag follows the version properly

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

.. because matrix_mautrix_signal_version is used in other places
which do not expect it. For example: `matrix_mautrix_signal_container_image_self_build_branch`

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

[#3031] Update mautrix-signal to the go version (signalgo merged to signal)

chore(deps): update halfshot/matrix-hookshot docker tag to v5.1.1

chore(deps): update halfshot/matrix-hookshot docker tag to v5.1.0

chore(deps): update dependency etherpad to v1.9.6-0

chore(deps): update halfshot/matrix-hookshot docker tag to v5

chore(deps): update dock.mau.dev/mautrix/telegram docker tag to v0.15.1

add automatic registration of chatgpt bot's user (if password is provided)

MMR reverse proxy updates

`matrix_media_repo_identifier` is already defined in the role defaults,
which is a better role to have it anyway.

Fix "SSL_do_handshake() failed" in nginx reverse-proxy

In nginx reverse-proxy, when the upstream server relies on SNI, the reverser-proxy may return 502 by follow error:
```
*10 SSL_do_handshake() failed (SSL: error:0A000410:SSL routines::sslv3 alert handshake failure:SSL alert number 40) while SSL handshaking to upstream, client: 172.19.0.1, server: example.host, request: "GET /.well-known/matrix/client HTTP/2.0", upstream: "https://<ip>/.well-known/matrix/client", host: "<domain>"
```
This problem often arises when the upstream server is behind the CDN, setting `proxy_ssl_server_name` to `on` will solve it.