RFE: ansible-navigator as playbook executor

[cidrblock]

As a user I want to use ansible-navigator to run one or all of the steps and provide configuration for the navigator command line.

This will allow users to test their collection content within an execution environment if desired.

Note: docker in docker, podman in docker, podman in podman, docker in podman are all "tricky". Will need to provide documentation here

[Qalthos]

molecule directly invokes ansible-playbook here: https://github.com/ansible/molecule/blob/main/src/molecule/provisioner/ansible_playbook.py#L112. The executable is parameterized, but is invariably set to "ansible-playbook" in bake() above. Will need to see what else needs to be replaced to make this something that can be switched out at will.

[simenon]

I would like to see this functionality in molecule. One of the big struggles that we are facing currently is that we are still stuck on ansible-core 2.9 for some projects, while the latest is ansible-core 2.17. This means that i can't specific target testing for ansible-core 2.9.

Additionally we make use of custom execution environments, which we would like to test with as well with molecule. Which is possible with ansible-navigator