(PUP-1722) Permit HTTPS and FTP protocols in yumrepo
(PUP-897) Allow rpm package provider to query by virtual package name.

Some providers that inherit from the rpm provider, such as the yum provider, do
a query after installing a package. If the package is specified by a virtual name,
the yum provider installs the package successfully, but the base rpm provider
implementation fails to query the installed package. This causes a confusing
"could not find package" error even though the package was installed.

Passing the '--whatprovides' option to rpm when performing a query instructs rpm
to locate packages that provide the given virtual name. This enables child providers
to install by virtual package name without errors.
Merge pull request #2370 from peterhuene/master

(PUP-897) Allow rpm package provider to query by virtual package name.
(PUP-1584) Expand some modulepath settings for windows

A couple of module_tool specs modified for PUP-1584 were not being
expanded such that they would work properly on Windows or POSIX.
Merge pull request #2363 from domcleal/tickets/master/pup-1722-yumrepo-protocols

(PUP-1722) Permit HTTPS and FTP protocols in yumrepo
Merge branch 'issue/master/pup-1584-expand-path-for-specs-on-windows'

* issue/master/pup-1584-expand-path-for-specs-on-windows:
  (PUP-1584) Expand some modulepath settings for windows
(maint) Release hosts to the vcloud pooling api

Our configurations now uses Scott's vcloud pooling api, so rather than
attempt to destroy them directly through vsphere (the code for which was
no longer working with current rbvmomi anyway) we are submitting them to
the pooling api for deletion.
(maint) Remove unused rsync for preserved acceptance test reruns

Package re-installation and rsyncing of local code changes while
re-running acceptance tests on preserved vms is something we aren't
doing. A better solution for the cycle of acceptance testing against
local changes is to use a git install against a local git daemon (see
the docs/acceptance_tests.md) to test against changes you have checked
in locally.
(maint) Pin to Beaker 1.6 and default to preserve_hosts onfail

Beaker can now be set to preserve hosts if the acceptance run fails.  We
are now defaulting to that for ci and manual testing, and pinning to
Beaker ~>1.6.2, so any release on the 1.6 line.