Update `ansible-compat` to v4.1.8 (ansible#4028)

Update ansible-compat to v4.1.8

Pass environment in testinfra (ansible#4014)

Related to ansible#4011

---------

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>

Update pre-commit (ansible#4007)

Ignore scenarios in virtual envrionments (ansible#3996)

Ignore scenarios in virtual environments.
This only works when repository is initialized with git otherwise just
returns all scenario files.

Fixes: ansible#3992

Update documentation (ansible#3985)

Update documentation for molecule.

Add example of integration with kubevirt (ansible#3972)

Greetings,

In our team, we handle important Ansible roles to configure various
aspects of RHEL systems, such as sshd, firewalld, grub, crypto-policies,
and more. Although we have implemented automated testing with Molecule
and Podman, there are instances where manual testing on our RHEL hosts
becomes necessary before we proceed with deployment. I propose the
integration of Molecule with Kubevirt as a potential solution to this
issue. Such an integration would allow us to quickly and effectively
test our Ansible roles on actual VMs, enhancing our testing procedures
and providing more reliable results.

Some benefits of testing on VMs:

1. **System-level realism**: Ephemeral VMs provide a complete, isolated
guest OS environment, much like your production environment. Containers
share the host's kernel and are not fully isolated. This difference can
occasionally lead to inconsistencies between testing and production
environments. With VM-based testing, you can ensure the roles will work
as expected on the actual operating system.

2. **Broader Compatibility**: Not all applications or configurations are
container-friendly, especially when they interact with the system at a
low level. VMs provide broader compatibility for testing as they offer a
full-fledged OS environment.

3. **Improved Debugging**: Since VMs provide an entire guest operating
system, it is often easier to debug issues related to system services,
kernel modules, and other low-level components.

4. **Greater Variety of Testing**: VMs can run different kernel
versions, different operating systems, or different system-level
configurations. In contrast, containers are somewhat limited by the
features and configurations of the host kernel.

In this pull request, I have utilized ephemeral VMs as a part of my
example to showcase the benefits of this approach. By harnessing the
capabilities of ephemeral VMs, we can test our Ansible roles in a highly
realistic environment that closely mirrors our actual production
environment, taking full advantage of the benefits outlined above.

This example serves as a practical guide to illustrate how a real-world
application of Molecule and Kubevirt integration can enhance our current
testing methods, enabling more realistic testing.

---------

Signed-off-by: Jose Angel Morena <jmorenas@redhat.com>
Co-authored-by: Jose Angel Morena <jmorenas@redhat.com>
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Co-authored-by: Ajinkya Udgirkar <ajinkyaudgirkar@gmail.com>

Update documentation (ansible#3975)

Remove testinfra verifier (ansible#3964)

Starting with v6, there will be no testinfra plugin. Instead those
wanting to use testinfra, will be able to call it using
`ansible.builtin.shell` from `converge.yml` playbook.

Closes: ansible#3920

Fix documentation links (ansible#3940)

Fixes: ansible#3933

Avoid using incompatible ansible-compat version (ansible#3906)

Related: https://github.com/ansible/ansible-compat/discussions/257#discussioncomment-5791460