Windows Support

At the moment there are some key blocks on using the plugin with Windows containers though I don't think these are very big issues. I'd love to PR support for it if you guys are okay with it? It seems to me that the bulk of the issues come from using `vagrant ssh-config` to get the setting which of course makes sense for Linux, however, on Windows this may not always work. My suggestion is that we have a toggle within the platform settings to use WinRM instead. This would instead use the settings output from `vagrant winrm-config` which should be enough to ensure a connection can be established.

Whilst it is possible to work around this issue you can effectively only have one Windows environment per scenario due to the way molecule uses the connection_options in it's schema. If we allow this to be overridden in molecule-vagrant, it bypasses this setting and therefore allows Windows environments to be used in exactly the same way as Linux which is something I'd love to see.

Start by tracing how the plugin currently uses `vagrant ssh-config` and Molecule's `connection_options` schema. Compare that flow with `vagrant winrm-config` and the proposed platform-settings toggle; done means Windows environments can use WinRM without the one-environment-per-scenario limitation while Linux behavior remains supported.

Written by the indexing model from the issue text.