Update vcloud-tools (and all deps)

Switch to using vcloud-tools 1.0.0, vcloud-core 0.10.0, and later versions
of all tools. We no longer need to specify each of the tools individually.

This is a big jump; the previous version of vcloud-tools wasn't published to
rubygems and predates vcloud-launcher and vcloud-net_launcher being split
out.
Fix vcloud-launcher catalog[_item] deprecations

These were renamed in vcloud-launcher >= 0.1.0:

- https://github.com/gds-operations/vcloud-launcher/commit/713e75f287070a47f56ff63eb33451cc178268ea
- https://github.com/gds-operations/vcloud-launcher/commit/ee149d5a648aa2b8bdbe87932e93a5393f73e87c
Rename vcloud-{configure-edge,edge-configure}

This tool was renamed in vcloud-edge_gateway 1.0.0:

- https://github.com/gds-operations/vcloud-edge_gateway/blob/v1.1.0/CHANGELOG.md#100-2014-06-04
[#68989754] Use vcloud-login for Jenkins

Cribbed from gds/govuk-provisioning@62a7923d6186c64e23362d44f194027cbc69932b

Use a shell wrapper, similar to that used by the vcloud-* integration tests,
which creates a temporary FOG_RC (not contain the password) and fetches a
`FOG_VCLOUD_TOKEN` using the new `vcloud-login` utility.

This script is sourced rather than executed so that the trap is called when
`jenkins.sh` exits. Rather than when `jenkins_vcloud_login.sh` completes.

I tried to think of ways to make this more re-usable across projects. The
only thing I could think of was rather horrible; a flag to vcloud-login
which outputs a lot of shell script that can be `eval`ed. I think we'll have
to put up with the duplication for now.
Merge pull request #57 from alphagov/68989754-use_vcloud_login

[#68989754] Use vcloud-login for Jenkins