docs/configuring-playbook: Add link to etherpad configuration

Add ability to sync only direct Chats in TG-Bridge

update docs to exclude grou-sync

add option to change filter_mode

add default for TG filter_mode

These Postgres configuration variables are part of the `database.yaml` file
and don't need to be here.

This allows people to augment the Synapse image with custom tools and
addons without having to rebuild it from scratch.

If customizations are enabled, the playbook will build a new
`localhost/matrixdotorg/synapse:VERSION-customized` image
on top of the default one (`FROM matrixdotorg/synapse:VERSION`)
and with custom Dockerfile build steps.

For servers that self-build the Synapse image, the Synapse image will be
built first, before proceding to extend it the same way.

In the future, we'll also have easy to enable Dockerfile build steps
for modules that the playbook supports.

In the future, we'll also inject media storage providers that we support
into the `matrix_synapse_media_storage_providers_auto` list.

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

Update postmoogle 0.9.6 -> 0.9.7

Update Caddy examples and outdated Jitsi docker env variable/documentation link

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

* fix room account data retrieving

Update grafana 9.1.7 -> 9.2.0

Update element 1.11.9 -> 1.11.10

Update postmoogle 0.9.5 -> 0.9.6

Update element 1.11.8 -> 1.11.9

* show recipient's email (header `TO`)
* add `norecipient` option
* add anti-spam options (`spamcheck:` and `spamlist:`)
* fix bugs

We don't like updating to untagged releases, but..

0.2.1 has some regression and upstream is not releasing 0.2.2 or 0.3.0
just yet, so we either need to downgrade to 0.2.0 or go `latest`.

We can hopefully switch back to a tagged release soon.

Related to https://github.com/mautrix/instagram/issues/56

Enable hookshot feeds by default

Change hookshot logging level to warn

all other bridges use that level

as per documentation: "Services that need no further configuration are enabled by default" and feeds service doesn't require it

fix(goofys): fix synapse systemd unit file to correctly require goofys

On Debian 10 (buster) at least, while the Synapse systemd service unit
was referring to Goofys as "matrix-goofys" without a ".service" suffix,
systemd was ignoring the goofys dependency, starting Synapse before
Goofys. All other dependant units which work are using the ".service"
suffix.

This generally leads to the mount path goofys using having been
populated by Synapse before Goofys starts, causing it to fail due to the
mount target not being empty.

The fix seems to be to ensure that the Synapse service unit refers to
Goofys as "matrix-goofys.service".

This change causes the following two lines in
"/etc/systemd/system/matrix-synapse.service":

    Requires=matrix-goofys
    After=matrix-goofys

To be changed to:

    Requires=matrix-goofys.service
    After=matrix-goofys.service