Podman plugins fails

hi,

Not so sure due to my polluted python environment, but seems like molecule podman is failing since 23.5.3

Configuration
```
[tool.poetry.dependencies]
python = ">=3.11"
ansible = "^11.5.0"
jmespath = "^1.0.1"
netaddr = "^0.8.0"

[tool.poetry.group.dev.dependencies]
flake8 = "*"
yamllint = "*"
tox = "*"
pytest-testinfra = "*"
# molecule = "25.1.0"
molecule-plugins = {version = "23.5.3", extras = ["podman"]} # Tested with newest, same problem
ansible-lint = { version = "v25.4.0", markers = "platform_system != 'Windows'" }
```

Error
```
failed: [localhost] (item={'failed': 0, 'started': 1, 'finished': 0, 'ansible_job_id': 'j343429397138.69239', 'results_file': '/Users/charliemordant/.ansible_async/j343429397138.69239', 'changed': True, 'item': {'cgroupns_mode': 'host', 'command': '/sbin/init', 'dns_servers': ['8.8.8.8'], 'dockerfile': '../common/Dockerfile.j2', 'image': 'fedora:38', 'name': 'routing.osgiliath.test', 'privileged': True, 'systemd': True, 'volumes': ['/sys/fs/cgroup:/sys/fs/cgroup:rw']}, 'ansible_loop_var': 'item'}) => {"ansible_job_id": "j343429397138.69239", "ansible_loop_var": "item", "attempts": 1, "changed": false, "finished": 1, "item": {"ansible_job_id": "j343429397138.69239", "ansible_loop_var": "item", "changed": true, "failed": 0, "finished": 0, "item": {"cgroupns_mode": "host", "command": "/sbin/init", "dns_servers": ["8.8.8.8"], "dockerfile": "../common/Dockerfile.j2", "image": "fedora:38", "name": "routing.osgiliath.test", "privileged": true, "systemd": true, "volumes": ["/sys/fs/cgroup:/sys/fs/cgroup:rw"]}, "results_file": "/Users/path/.ansible_async/j343429397138.69239", "started": 1}, "msg": "could not find job", "results_file": "/var/root/.ansible_async/j343429397138.69239", "started": 1, "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []}

```

May you please double check?

Reproduce the Molecule Podman scenario with the listed Python, Ansible, and molecule-plugins versions, then investigate the reported async job result around the Fedora systemd container run. Done means the scenario completes without “could not find job” and the regression is covered by a test.

Written by the indexing model from the issue text.