Fog::Compute::VcloudDirector#get_vdc takes ID

Fog::Compute::VcloudDirector#get_vdc takes an ID as its argument[1],
rather than a name.

[1]:
https://github.com/fog/fog/blob/a1c1649d5166da4f7c16a3c89e9121112d3b7a99/lib/fog/vcloud_director/requests/compute/get_vdc.rb#L15
get_organization takes ID rather than a name

Fog::Compute::VcloudDirector#get_organization takes an ID as its
argument[1], rather than a name.

[1]:
https://github.com/fog/fog/blob/16db605f9ae35adfe2b926dee2e4cd669b435455/lib/fog/vcloud_director/requests/compute/get_organization.rb#L15
s/test_data/test_params/

Rename `test_data` to `test_params` for consistency with the
naming of the `Vcloud::Tools::Tester::TestParameters` class.
Use new TestSetup interface to access test params

As of version 0.1.0 of the vCloud Tools Tester gem, we must use the
`Vcloud::Tools::Tester::TestSetup#test_params` method to retrieve test
parameters.

Also, update the gemspec file to reflect this.

* * *

Note that I've intentionally left the `expected_user_params` argument
for `TestSetup#new` empty; this is new functionality that was added in
vCloud Tools Tester version 0.1.0 and is outside the scope of the
current story.
Merge pull request #88 from gds-operations/67916012-integ-setup

[#67916012] Use new TestSetup interface to access test params
Specify the required user-defined test params

By specifying the user-defined test parameters we require for each test,
vCloud Tools Tester will fail fast if these parameters are not defined.
(Re)move preamble processing. Now in Vcloud::Launcher::Preamble.

configure_guest_customization_section now just takes a single
pre-templated/pre-processed script that will be passed to Fog.
Merge pull request #89 from gds-operations/72866380-required-user-params

[#72866380] Specify the required user-defined test params
Merge pull request #90 from bazbremner/move_preamble_processing

[#66849308] (Re)move preamble processing. Now in Vcloud::Launcher::Preamble.
Version 0.6.0

Bump the minor version to reflect breaking changes to
`Vcloud::Core::Vm#configure_guest_customization_section`. Make this a
minor bump despite the backwards-incompatible change as we're not yet at
version 1.0 so that API is expected to be unstable[1].

[1]: http://semver.org/
Update CHANGELOG for 0.6.0

Update the CHANGELOG to reflect changes to
`Vcloud::Core::Vm#configure_guest_customization_section` and the minimum
supported Ruby version in version 0.6.0.
Merge pull request #91 from gds-operations/update-changelog

[#74382904] Update CHANGELOG and release version 0.6.0
Relax dev dep on vcloud-tools-tester

In gds-operations/vcloud-tools-tester#18 we bumped `vcloud-tools-tester`
to version `0.1.2` when resolving a cyclical runtime dependency on
vcloud-core. We now need to relax the development dependency here to
allow vcloud-core to build, at which point we can publish new versions
of the other gems.
Merge pull request #92 from gds-operations/relax-dev-deps

Relax dev dep on vcloud-tools-tester
Rename s/CommandRun/QueryCommandRun/

Because I need to use similar code in another test and:

- the names can't clash
- I can't figure out how to share this as a helper
Add vcloud-login utility for session tokens

As described by the --help argument:

    Usage: ./bin/vcloud-login [options]

    Utility for obtaining a Fog vCloud Director session token. It will output a
    shell `export` command that can be consumed with:

        eval $(FOG_CREDENTIAL=example ./bin/vcloud-login)

    It requires a Fog credentials file (e.g. `~/.fog`) with the host and user
    set, but the password set to an empty string. The password will be prompted
    for interactively.

This should serve to consolidate the various scripts other teams have needed to
create in order to follow the advice about not storing plaintext passwords in
the fogrc file.
Update README to reference new vcloud-login

Simplify the instructions for fetching a session token by using the new
vcloud-login utility. This will also need to be applied, or better
referenced, by the other projects once merged.
Move Vcloud::Core::Login to Vcloud::Fog::Login

Because this class is strictly concerned about interacting with Fog -
setting/checking credentials and logging in. This follows the pattern of
putting all of our direct-Fog interactions into a single namespace, so that
we can refactor them if required at a later date.
Don't use Fog.credentials to set password

Modifying the global credential hash feels quite magic, when we could just
pass the necessary argument into the VcloudDirector class, which will
override the credentials.

By accessing Fog directly, rather than through
Vcloud::Fog::ServiceInterface, we can also modify our abstractions to Fog in
order to make them always require a token and raise an exception if they
find a plaintext password. This will come at a later date.
Allow vcloud-login password to be piped in

The highline gem pretty much does this for us. All we need to do is change
the prompt to make it clear that it's reading data, and not output the
masked password. This will make it easier for us to use this login method in
CI where Jenkins has the password as an environment variable.