fix: make role compatible with podman

[JonasPammer]

Fixes robertdebock/ansible-role-bootstrap#66 as described in said PR

Checked this myself.
Made this to give myself an reason to try out to install and use podman.
As I couldn't get rootless podman to work with my network linux user (official not supported note can be found here) I'll still stay away with it though

Without this, following error would occur:

TASK [ansible-role-bootstrap : Install bootstrap packages (raw).] **************
Mittwoch 31 August 2022  18:13:06 +0200 (0:00:00.111)       0:00:03.506 *******
fatal: [instance-py3-ansible-4-debian10]: FAILED! => changed=true 
  msg: non-zero return code
  rc: 127
  stderr: |-
    Error: executable file `LANG=C` not found in $PATH: No such file or directory: OCI runtime attempted to invoke a command that was not found
  stderr_lines: <omitted>
  stdout: ''
  stdout_lines: <omitted>

... even with bootstrap_become: false (default).

Note: As per https://github.com/actions/runner-images/blob/ubuntu20/20220821.1/images/linux/Ubuntu2004-Readme.md, the current Github Ubuntu VM image ships with podman preinstalled, so there was or should not be a need to change the workflow.

Required Checklist

• Documentation has been altered or extended appropriately
• This pull request and its commits address only a single concern
• I have followed JonasPammer's Ansible Role Development Guidelines
• I am a nice guy

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

Optional Checklist

• pre-commit was installed in local development environment (if not, a GitHub workflow will run pre-commit once you create the request)

• my commits are small, single-purpose, detailed and maybe even follow the conventional commit specification for extra convenience of the reviewer

[JonasPammer]

A prove of this bug can be found in a CI run that was run before 63d5a36 (fix: add executable …) was commited: https://github.com/JonasPammer/ansible-role-bootstrap/runs/8118241659?check_suite_focus=true (sorry for the force push which gobbled the commits)

[JonasPammer]

lgtm when CI finishes!

[JonasPammer]

This PR also addresses the problem as reported by robertdebock/ansible-role-bootstrap#55. Although this issue has no further comments or reactions I link to it here anyway so people stumbling upon it find this.

[JonasPammer]

Currently errors on all variations of CI as tested in https://github.com/JonasPammer/ansible-role-bootstrap/actions/runs/2966687600, dont have time to investigate today

[JonasPammer]

My current analysis is that the problem boils down to molecule assuming the following in CI, which is not true.

Molecule podman > create
  WARNING  Skipping, instances already created.

There is no difference in pip package versions between CI and local testing i did. only difference currently can think of is that i need to run tox with sudo because podman requires root and i can't setup rootless with my network user setup i currently have

[JonasPammer]

it seems to sportically work?
re-run normal all distro all ansible version workflow: debian passes both 4/5, fedora35 passes ansible-4 but fails ansible-5 https://github.com/JonasPammer/ansible-role-bootstrap/runs/8169369821?check_suite_focus=true

[JonasPammer]

ok. as i am not using podman myself imma remove it from test suite. its molecule collection and extension also says its early stage :/. but i'm going to leave this PR and the actual task adjustment because as seen it does fix podman.