Clean VMX step should always remove floppy.

When using the VMX builder its possible for the source machine to have a floppy configured which gets cloned to the new VM Packer spins up. When the new VM's Packer config doesn't have a floppy_files config entry, the Packer clean VMX step fails to remove the floppy disk from the new VM. This can cause build failures, for example with the vsphere post processor; generating errors like:

* Post-processor failed: Failed: exit status 1
Error: File (/home/teamcity/tmp/buildTmp/packer941120499) could not be found.

Opening the cloned VM's VMX file you can clearly see it has a floppy entry from the source machine's VMX file (exact same path) even though the Packer config contains no floppy_files entry.
builder/parallels: Ignore 'The fdd0 device does not exist'

A current floppy disk probably doesn't exist, so the build shouldn't
fail when we try to delete it.
GH 1508 - Ensure Packer VMX is updated and saved

We need to ensure the VMWare process has exited before attempting to run VMX file cleanup steps, otherwise VMWare may overwrite our changes. While Packer does its best to ensure VMWare has exited, there's still a race condition on some OSs between VMWare flushing the VMX and Packer updating it. The workaround is to artifically wait 5 seconds.

When using the VMX builder its possible for the source machine to have a floppy and/or CD-ROM mounted which gets cloned to the new VM Packer spins up, but have no Packer configuration for those devices. With this change we always attempt to remove the mounted devices regardless of the Packer configuration.
Minor edits
make docker-push work with docker-tag artifacts
Ditch ` around content words
Update chef-solo.html.markdown
Update amazon.html.markdown

Technical correction
Fixed dead links in doc section environment-variables.

Due to a missing `/` the links pointed to i.e. `docs/other/docs/other/core-configuration.html` producing a 404 / Page not found.
builder/parallels: Init VM without hdd and attach it later

Avoid the disk resize because it is unsupported for some guests (OS X)
http://kb.parallels.com/en/113653
Fix for panic when ssh min and max port is the same for qemu builder. Taken directly from a previous patch by mitchellh 8f50d2dd9a5b943881f0827fc07fbfb389e1407c
Changing machinetype default to PC instead of PC-1.0 which seems to be a saner default that works on more platforms. RedHat in particular doesnt have PC-1.0
-redir is deprecated and missing on some versions of QEMU, using -netdev instead which is recommended. Removing M letter from Memory flag as QEMU now assumes this value is always in MB and errors out if you pass the M as a part of the command
Remove unnecessary counter file (as per @pearkes)
Update website to use latest middleman
Merge pull request #1501 from JessThrysoee/current_fdd0_does_not_exist

builder/parallels: Ignore 'The fdd0 device does not exist'
Merge pull request #1554 from mitchellh/sethvargo/update_middleman

Update website to use latest middleman
builder/parallels: Rely on Cleanup functions to detach devices

Remove the redundant StepRemoveDevices and rely on the cleanup to be handled by:
* StepAttachParallelsTools.Cleanup
* StepAttachFloppy.Cleanup
* stepAttachISO.Cleanup
builder/parallels: Added driver method 'DeviceAddCdRom'
builder/parallels: Attach ISO images to the separate cdrom device

For each ISO image the individual cdrom device will be added to the VM. During the cleanup these devices will be deleted.
It makes attach steps more clear - there is no doubt what is the name of the device.

Related to: [mitchellh/packer#1502]