windows based instances do not work using default template

@jgoldschrafe 's excellent work on the create/destroy templates significantly degrade windows support. To me the killer feature of molecule-ec2 of using docker is the support for Windows based hosts.

The default cloud-init key inject method doesn't create or associate an ec2 based key. This is required to extract the default random windows password from AWS.

The default security group only permits ssh access, it doesn't allow the winrm ports or rdp. These should be safe to open as they don't overlap with significant linux services.

The image user data is hard coded to be cloud-init yaml content. For a Windows image this should be powershell. The structure of passing a dict via platform_cloud_config which is converted to yaml will not work for Windows user_data.

Waiting for the ssh port to come up also doesn't work on a host which doesn't use ssh. Changing the port is insufficient as the test looks for the ssh connection response.

The issue names no files or tests. Start by tracing the create/destroy templates and the default key injection, security-group, user-data, and readiness checks; compare their assumptions with Windows EC2 behavior. Done means Windows instances can obtain their password and support the required WinRM, RDP, and readiness paths.

Written by the indexing model from the issue text.