RFE: New molecule.provisoning collection

[cidrblock]

As a user I want to provide playbooks used for provisioning to a community supported collection to other users.

Similar to the molecule plugin python package I think we should have a collection/repo intended to be used as a landing for well vetted , commonly used playbooks using the default provisioner.\

This may resolve many of the issues I suspect we will enounter related to sprawl and discovery if we don't facilitate reusability.
These can be immediately usable or at least serve as references

Some of the things we will need to resolve:

• per playbook documentation, ansible (today) does not have a convention for playbook adjacent or sidecar documentation.
• how do handle destroy (e.g. playbook naming conventions/directory structures)
• per play argspec validation, ansible (today) does not have a convention for argspec validation at the play pre execution to ensure all vars necessary for execution have been provided
• packaging, testing, all other CI related activites

[tima]

I like the idea of collections for Molecule here. I'd recommend we leave the naming open to many provisions. So molecule.core for main/default/supported provisioners and using the molecule.* convention for others whether they come from the community, partner or an IT org creates something of their own.

[Qalthos]

A good start for this collection could be including the examples as roles, for example https://ansible.readthedocs.io/projects/molecule/examples/podman/