The local development system was updated from Debian/bullseye to
Debian/bookworm. Podman works well, so we switched Ansible Molecule
from docker to podman.

We now also use a custom podman container with ansible-core v2.16.14, so
we use this version for the default Ansible Molecule configuration.

Ansible-core does not come with the community.general collection which
is included in Ansible only. See Ansible 9 Release Notes which contains
ansible-core 2.16.14:
* https://docs.ansible.com/projects/ansible/latest/reference_appendices/release_and_maintenance.html#ansible-community-changelogs
* https://github.com/ansible-community/ansible-build-data/blob/main/9/CHANGELOG-v9.rst#ansible-core

This role needs community.general.alternatives, so we have to add a
"community.general" collection dependency in requirements.yml.

It was also a bad idea to not set an ansible(-core) version in the
requirements.txt as the user always gets the latest ansible(-core) +
molecule version when calling "make install" or "make upgrade", which
might lead to unexpected results.

For instance, Ansible Molecule dropped their default `ansible_managed`
value because it's deprecated in ansible since v2.19.

This causes "molecule verify" to fail:

  TASK [Deploy chrony with server configuration] *********************************
  --- before: /etc/chrony/chrony.conf
  +++ after: /home/jkirk/projects/ansible/ansible-role-base/molecule/default/files/chrony.bookworm.example.conf
  @@ -1,4 +1,4 @@
  -# Ansible managed
  +# Ansible managed: Do NOT edit this file manually!
   # Welcome to the chrony configuration file. See chrony.conf(5) for more
   # information about usable directives.

  changed: [instance]

  TASK [Assert generated default chrony with server configuration] ***************
  [ERROR]: Task failed: Action failed: Unexpected change in /etc/chrony/chrony.conf
  Origin: /home/jkirk/projects/ansible/ansible-role-base/molecule/default/verify.yml:19:5

  17     diff: true
  18
  19   - name: Assert generated default chrony with server configuration
         ^ column 5

  fatal: [instance]: FAILED! => {
      "assertion": "not chrony_server_example_conf.changed",
      "changed": false,
      "evaluated_to": false,
      "msg": "Unexpected change in /etc/chrony/chrony.conf"
  }

This happened in Ansible Molecule v25.11, see:

- ansible/molecule#4553
- ansible/molecule@a75761e

There are now (since Ansible Molecule v25) two ways to set
`ansible_managed` in ansible.cfg:

- Ansible-Native configuration, see: https://docs.ansible.com/projects/molecule/ansible-native/
- Pre ansible-native configuration: see:
  https://docs.ansible.com/projects/molecule/configuration/#provisioner-pre-ansible-native

To be backward compatible to Ansible Molecule v24 which is the last
version which works with ansible-core 2.14 (which ships in
Debian/bookworm), we set `ansible_managed` in the provisioner
configuration.

Also decided to drop ansible-lint and yamllint, as it is not called
automatically.