Fix for hookshot validation failure

Update chatgpt 3.1.0 -> 3.1.2

Update mautrix-instagram 0.2.3 -> 0.3.0

Update mautrix-facebook 0.4.1 -> 0.5.0

Fix prefix path when loading Hydrogen's theme-element.json

Revert "Revert "Update hookshot 4.0.0 -> 4.1.0""

Update Draupnir to 1.83.0 from 1.82.0

This reverts commit f98f803b44.

As the docker image has been released for this version we can now upgrade to this version

This is needed when using a prefix path that doesn't end with a slash.

Signed-off-by: Sergio Durigan Junior <sergiodj@sergiodj.net>

Document how to use chatgpt-bot in encrypted rooms

Update prerequisites.md

added an extra step to creating the chatgpt bot so it can read encrypted messages

These ports need to be open in order to receive emails to the Postmoogle bridge

update prometheus-node-exporter 1.5.0 -> 1.6.0

update mautrix-telegram 0.13.0 -> 0.14.0

Update synapse 1.84.0 -> 1.84.1

This reverts commit 428f7a1f75.

Looks like it won't become a tagged image until a "release" is posted.

add updated Caddyfile example

Update Draupnir from 1.80.1 to 1.82.0

Related to:

- https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2698
- https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2700

Update hookshot 4.0.0 -> 4.1.0

update synapse 1.83.0 -> 1.84.0; set forget_rooms_on_leave = true

Update mautrix-twitter 0.1.5 -> 0.1.6

Bump frenck/action-yamllint from 1.4.0 to 1.4.1

Bumps [frenck/action-yamllint](https://github.com/frenck/action-yamllint) from 1.4.0 to 1.4.1.
- [Release notes](https://github.com/frenck/action-yamllint/releases)
- [Commits](https://github.com/frenck/action-yamllint/compare/v1.4.0...v1.4.1)

---
updated-dependencies:
- dependency-name: frenck/action-yamllint
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

This restores consistency with other services.

Related to 8f903fa621

This was mostly affecting the stream writer (events) worker, which was
being reported as unhealthy. It wasn't causing any issues, but it just
looked odd and was confusing people.

As an alternative to hitting the regular `/health` healthcheck route (on
the "client" API which this stream writer does not expose),
we may have went for hitting some "replication" API endpoint instead.

This is more complicated and likely unnecessary.

update ntfy 2.4.0 -> 2.5.0