IBMSCE is now aware of the `__active_profile_name__` context variable. Refs #546
Joyent is now aware of the `__active_profile_name__` context variable. Refs #546
Libcloud AWS is now aware of the `__active_profile_name__` context variable. Refs #546
Linode is now aware of the `__active_profile_name__` context variable. Refs #546
OpenStack is now aware of the `__active_profile_name__` context variable. Refs #546
Parallels is now aware of the `__active_profile_name__` context variable. Refs #546
Rackspace is now aware of the `__active_profile_name__` context variable. Refs #546
Renamed `__active_profile_name__` into `__active_provider_name__`.
EC2 is now aware of the `__active_profile_name__` context variable. Refs #546
Every salt-cloud module function is now executed using the cloud provider context. Fixes #546
Renamed `build_lookup` into `lookup_providers`
If a profile extending another can't find it, remove it from the listing.
Running actions now properly works with the new internal data layout.
The profile to run should be explicitly passed. API +1
We can now fail sooner.
Names should also be passed explicitly. API +1
Creating a machine using a specific profile now works with the new internal data layout.
Allow queries to be cached.
Deploying VM's using a map now properly works using the new data layout.

Information is shown for already running vms and also any errors found.
There's no reason why `libcloudfuncs_destroy` cannot be namespaced at module level