`matrix_nginx_proxy_enabled` is usually set to false by users, this is when
the warning should be displayed.

This fixes parameters not being passed to the provisioning api

Hello, this PR should fix Hookshot container not receiving API calls with the right path because nginx proxy was stripping the /v1 from it.

all features were actually already silently supported 🎉

upstream changelog: https://github.com/matrix-org/matrix-hookshot/releases/tag/1.2.0

to proxy url params in GET requests

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

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

based on comments in chat:
https://matrix.to/#/!TlZdPIYrhwNvXlBiEk:half-shot.uk/$RbG6itEHVV8J_u5ry1HiFdC76n19M3vmopfQOyRmkKU?via=half-shot.uk&via=matrix.org&via=envs.net

Reverts b1b4ba501fdfaa, 90c9801c560b6, a3c84f78ca9c65a, ..

I haven't really traced it (yet), but on some servers, I'm observing
`ansible-playbook ... --tags=start` completing very slowly, waiting
to stop services. I can't reproduce this on all Matrix servers I manage.
I suspect that either the systemd version is to blame or that some
specific service is not responding well to some `docker kill/rm` command.

`ExecStop` seems to work great in all cases and it's what we've been
using for a very long time, so I'm reverting to that.

using b33ea48

see Half-Shot/matrix-hookshot#167

needed for users to put private-key.pem in

see also #1527

https://github.com/Half-Shot/matrix-hookshot/issues/133#issuecomment-1007541580