Allow cloud information to come from pillar data
Document using Pillars for cloud config
Overwrite opts with what is in the pillars

I want to include all the things from the pillars, and have them
override everything that would be in the cloud configs.  We can make it
so that they do not update variables if it is already defined in
/etc/salt/cloud*, but I feel this way is better.
space pillar data better
format the profiles like salt-cloud is expecting them

inside the provider.
We use cloud instead of clouds everywhere else
simplify conditions in utils.network due to short-circuit eval
Cloud profiles need the profile name inside
if cache dir doesn't exist, make it
Merge pull request #12925 from hulu/simplify-conds

simplify conditions in utils.network due to short-circuit eval
Updated the troubleshooting index with some link fixes for 12791.
Merge pull request #12926 from gravyboat/develop

Updated the troubleshooting index with some link fixes for 12791.
copy pillars before acting on them

If we do the .pop() then they dictionary won't exist the next time
we come back to it when we do multiple calls to the cloud module inside
cloud states.
Updated the quickstart so we can get rid of the standalone minion docs.
Merge pull request #12927 from gravyboat/develop

Updated the quickstart so we can get rid of the standalone minion docs.
should be using pop for a clean update later
Fix indentation

This brings the note about the gitfs walthrough outside of the YAML
code-block.
Correct inaccuracies in gitfs walkthrough

Also, added some information on upcoming features
Merge pull request #12931 from terminalmage/docs

Correct inaccuracies in gitfs walkthrough
Merge pull request #12924 from gtmanfred/cloud

Include salt cloud modules configurations from pillars