Reogarnising the playbooks and the molecules scenarios

[rpelisse]

@rmarting I've reorganized our playbooks and molecule scenario to be more consistent with the Ansible best practices. Most of our playbooks inside the folder playbooks are actually advanced scenarios (advanced examples) and not really "ready to be used" playbooks. So instead using import playbook in the converge (which also not recommanded), I've move them into their own scenario. I've added to the playbooks folder ready to be use playbook to set up a brokers, zookeepers, connect or control cruise. So now, collection users can simply provides (for instance) the inventory of their brokers and directly run the playbook we provided:

$ ansible-playbook -i inventory middleware_automation.amq_streams.brokers

PS: Fun fact, doing the reorg, I stumble upon the same bug you had in your blogpost! That's one of the reason, it was good to move those playbook into the molecule scenario, better control of their content.

[rmarting]

I am not an Ansible tester expert with Molecule, however this organization is better than the previous one. Adding more complex (or advance) scenarios in molecule will give us a safe scenario for any new change done in the collection, and showing sample cases in the playbooks folder is a good starting point.

However, I am thinking that we should add some of the molecule scenarios as chapters or sections in the documention. I don't think the readers will go throught the molecule folder to get more advance examples.

In any case, LGTM!