Ref: https://github.com/matrix-org/matrix-hookshot/pull/1004

Ref: https://openai.com/index/introducing-gpt-5/

Related to https://github.com/devture/com.devture.ansible.role.playbook_runtime_messages/issues/1

Ref: https://github.com/element-hq/lk-jwt-service/releases/tag/v0.3.0

On ansible-core 2.19.0, invoking macro like this (which only outputted
something in its `if` block, not in `else`), resulted in a macro
outputting `None`.

One way to work around it is to add an explicit `else` block which also
outputs something.

A better way to work around it is to only invoke the macro if it
has something to output.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/4458

ansible-core>=2.19.0 only auto-parses YAML files, not JSON.

Previous ansible-core versions auto-parsed JSON as well, but ansible-core>=2.19.0
doesn't, so we added a `from_json` post-filter.
However, older versions auto-parsing JSON and turning it into a dict, on
which we later run `from_json` is no good.

In this patch, we try to equalize behavior and configure Ansible to never parse JSON,
hopefully making old-Ansible behave like new Ansible.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/4458

Ref: https://docs.ansible.com/ansible/latest/collections/ansible/builtin/template_lookup.html#parameter-convert_data

We expect a string, which is parsed via `from_json`.

This matches previous usage in inventories, as well as what the
user-controlled precedessor of this variable (`matrix_synapse_admin_configuration_extension_json`)
is like.

Related to 997e6ca611

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/4459

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/4445