* Update matrixdotorg/mjolnir Docker tag to v1.8.1

* Upgrade Mjolnir to v1.8.3

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Slavi Pantaleev <slavi@devture.com>

Revert Mjolnir version to 1.7.0 due to severe breakage.

The new prompt makes use of the new `baibot_conversation_start_time_utc`
prompt variable, which is not a moving target (like `baibot_now_utc`)
and as such allows prompt caching to work.

Ref: https://platform.openai.com/docs/guides/prompt-caching

Since 2024-10-02, `gpt-4o` is actually the same as `gpt-4o-2024-08-06`.

We previously used `gpt-4o-2024-08-06`, because it was pointing to a
much better (longer context) model. Since they're both the same now,
we'd better stick to the unpinned model and make it easier for future
users to get upgrades.

Update nginx Docker tag to v1.27.2

synapse-admin: authenticated media and options to delete media and redact events on user removal

Update matrixdotorg/mjolnir Docker tag to v1.8.1

Update docker.io/metio/matrix-alertmanager-receiver Docker tag to v2024.10.2

Update matrixdotorg/mjolnir Docker tag to v1.8.0

Update dependency grafana to v11.1.7-0

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

Update ghcr.io/element-hq/synapse Docker tag to v1.116.0

Update vectorim/element-web Docker tag to v1.11.79

Fix validate_config.yml

`devture_postgres_*` -> `postgres_*`

Upgrade Jitsi (v9646-1 -> v9753-0)

synapse-admin v0.10.3-etke17: add `Contact support` menu item

enable hookshot outbound webhooks

* WIP: add system-managed users to synapse-admin

* add missing users

* synapse-admin v0.10.3-etke15: Upgrade to react-admin v5

* v0.10.3-etke16

* fix linter

* add _auto and _custom vars

* Use 2 spaces before #noqa var-naming

---------

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

Update vectorim/element-web Docker tag to v1.11.78

`gpt-4o` will point to `gpt-4o-2024-08-06` after 2nd of October 2024
anyway. At that time, we can revert to pointing to `gpt-4o`.

The reason `gpt-4o-2024-08-06` was chosen now instead of `gpt-4o`:

- the `max_response_tokens` configuration was set to 16k, which matches
  `gpt-4o-2024-08-06`, but is too large for `gpt-4o` (max 4k)

- baibot's own configs for dynamically created agents, as well as static
  config examples use `gpt-4o-2024-08-06` and the larger
  `max_response_tokens` value

The playbook did not use to define a prompt for statically-defined
agents.

Since prompt variables support landed in v1.1.0
(see 2a5a2d6a4d)
it makes sense to make use of it for a better out-of-the-box experience
(see https://github.com/etkecc/baibot/issues/10).

Update dependency etherpad to v2.2.5-0