Adding the conditional necessary to construct the right  options for both PV and HVM images. Also adding a test to make sure it is doing the right thing

mount /dev/xvdf /mnt/point
while for an HVM image that is attached to /dev/sdf, its mount command is
mount /dev/xvdf1 /mnt/point
so this code enabled that

To be able to build both PV and HVM images, it is not possible to use both /dev/sd[f-p] and [1-16] as the HVM images get attached at /dev/sdf but must be mounted a /dev/sdf1.

This reduces the number of simultaneous packer runs possible significantly, but unless you are Netflix, who have Aminator anyway, this is probably never going to be an issue

Update GCE source_image in the docs

builder/googlecompute: rename "Gsutil" to "Gcloud" now that we're updating "gcloud" and not "gsutil".

Also renamed files accordingly.

builder/googlecompute: added support for all standard VM images

[GCE] google compute builder is broken, gsutil update fails in newer images

Do not re-add floppy disk files to VMX

This commit fixes errors like this in the vsphere post-processor when using floppy files in the builder step:
Error: File (/var/folders/zl/57c1vmr532z_ryf1scw53_b9ycmxh7/T/packer964492999) could not be found

The configure VMX step re-adds the floppy files, so we need to configure the VMX and _then_ clean the VMX in that order.

Added support to use templates for more fields in null-builder and amazon-builder

builder/amazon: support for enhanced networking

website: Added documentation page for environmental variables. #1130

website: Fixed Rackspace example

builder/vmware/esxi: checksum iso upload to not always upload

builder/virtualbox: Accept VirtualBox release candidate version

packer: Fixed typo in error message

website: Specifically call out the comma after `"builders": [...]`

Install gox during build time

post-processor/vagrant: hyper-v

Just so that we can just run `make` without installing gox separatelyy

Cleaned up Go formatting with gofmt.