Create issues in individual collections to migrate their scenario guides

[samccann]

Scenario guides that are specific to a collection should no longer be in the ansible/ansible repository. Open issues on the following collection repos to request they move their guides. Point to the following in each issue on how to do this:

https://hackmd.io/w6JSHW_XRzi9cBZtoN4snA?view

[samccann]

• vmware_rest_scenarios
• guide_aci.rst
• guide_alicloud.rst
• guide_aws.rst
• guide_azure.rst
• guide_cloudstack.rst
• guide_docker.rst
• guide_gce.rst
• guide_infoblox.rst
• guide_meraki.rst
• guide_oracle.rst
• guide_packet.rst
• guide_rax.rst
• guide_scaleway.rst
• guide_vagrant.rst
• guide_vmware_rest.rst
• guide_vultr.rst

[samccann]

The following boilerplate text can be used in the collection-level issue:

Collection-based scenario guides must live in their respective collections going forward. This ensures the guides are updated and kept in sync with the collection release.

The Ansible documentation code will take this collection-level guide and publish it along with your collection on docs.ansible.com.
See https://docs.ansible.com/ansible/latest/collections/community/dns/index.html#guides for an example of how this shows up once a guide is moved into the collection repo.

See https://hackmd.io/w6JSHW_XRzi9cBZtoN4snA?view For steps on how to do this.

The XX guide rst file is [here](appropriate url taken from links in prior comment).

[samccann]

See how a script opened a batch of issues on collections in #60

We should target this for April to spread out the batch issue opens a bit.

[samccann]

See https://forum.ansible.com/t/removing-old-stale-scenario-guides/2761/31 for discussion.