Instead of requiring

- roles
  role: role_name
  p1: v1

we can now do

- roles
  role_name
  p1: v1

or even

- roles
  role_name: v1

depending on how the role interprets the
parameters.

Provider-specific extensions can modify the VM; the hostscript
extension allows running local scripts pre- or post-provisioning.

Otherwise, our abilities to do things in the extension method are
too limited.

Names and upload paths avoid that several provisioners end up
being /tmp/vagrant_shell

Default vagrant provisioners are nice to be able to use directly
from the box definition without having to make a dedicated role.
By treating them structurally like other roles, we can keep the
main Vagrantfile somewhat clean from special case handling.

Only special case is scripts, which might use environment variables
that should not be expanded on the host, but on the guest. Those we
need to allow to not be expanded, and so we use $$ for those.

Rather than inserting a disk, install mingw via chocolatey. The
script is fairly generic, and accepts package name and version
overrides via role parameters.

To support this, add the relevant support to the provisioning
generator in the Vagrantfile.

The generic windows-tools role becomes a bit simplier so that it
is also useful for mingw. cmake, jom, and llvm are not strictly
needed by MSVC either anyway.

Previously, we tried to load WinRM for each Windows box, and
selected the winrm communicator when this succeeded. With the
latest upgrade of vagrant, only the first loading attempt
succeeded, all others failed but without throwing an exception.
So we incorrectly fell back to the winssh communicator, but
without the corresponding message.

With this change, the has_winrm variable becomes global, and we
only try to load the winrm gem if it's false.

With the VMware tools installed, we can share folders
using standard vagrant mechanisms, without having
to go through sshfs.

After the last changes, expanding the private key for private
boxes was broken, as it remained in the box. With this change,
it gets removed and moved into the URL before other environment
variables are expanded.

To test this, expand the set of mocking classes quite a bit so
that we can actually execute the bulk of the Vagrant file, and
capture some of the settings made for the virtual machines.

Knows something about how to install a number of environments
on Ubuntu and CentOS based systems. Use "desktop" parameter in
the role to state which environment to provision with, ie

- name: kde
  box: generic/ubuntu1804
  roles:
    - role: linux-desktop
      desktop: kde

Makes it easier to test provisioning.

boxes.xml can override defaults using respective parameters.

Works only with VMWare provider, but now possible to run emulator
within the android-builder VM.

Boxes that rely on provider-specific features, such as VM nesting,
can state which provider they prefer.

With this, the Android emulator passes the acceleration check.

Implement folder sharing and disk support, hiding the differences
between VMWare and VirtualBox.

Add basic scripting for packaging an existing VMWare machine into
a vagrant base-box. Exporting a pre-built basebox from VirtualBox
as an OVA, then importing it into VMWare, then packaging it.

With this change, Windows cmd and bash on hosts both
can handle quoted arguments with spaces correctly, no
matter whether

--arg "foo bar"
--arg foo,bar
--arg \"foo bar\"

A help file that's placed with the job scripts and
contains the text is a trivial solution.

Speed up Windows build by only building debug

See merge request vohilshe/qt-developer-environments!4