Change invocation of EdgeGateway::Configure

Move the config and template arguments to the initialiser so that:

- It behaves more like a class than a module. So that you instantiate it
  with a config and then call update on that object, which feels more
  natural than doing `foo.new.update()`.
- We can perform schema validation early and separately from applying the
  update. Which will be particulary useful when we expose a `--validate`
  argument in [#69717072].
Remove orphaned files

These files aren't referenced anywhere as far as I can tell and don't
seem to belong to vcloud-edge_gateway (perhaps they were used for
vcloud-launcher?).
Merge pull request #64 from alphagov/remove-orphaned-files

Remove orphaned files
Merge pull request #62 from alphagov/move_config_to_init

Change invocation of EdgeGateway::Configure
Refactor vcloud_pool_healthcheck_entry array

Refactor vcloud_pool_healthcheck_entry array to remove the default_mode
variable.

Given that all other defaults are defined line-by-line, I don't see why
the `:Mode` key should be any different.
Don't set healthcheck URI for non-HTTP checks

Don't set a healthcheck URI for non-HTTP load balancer healthchecks.

In vCloud Director version 5.1 and 5.5, VMWare does not support a
healthcheck URI for SSL healthchecks[1]. In vCloud Director version 5.5,
a load balancer will refuse connections if a health check URL is set for
an SSL healthcheck.

TCP healthchecks obviously do not support a healthcheck URI given they
do not operate at layer 7.

This also fixes an issue related to
ecfba3960d8ae44169af81afd36647926226de15; that commit checks for a pool
service protocol of HTTP and sets the healthcheck URL accordingly. The
changes there did not however account for configurations where the pool
uses HTTP as the service protocol but TCP for the healthcheck.

The logic here is necessarily complex because we deal with:
  - defined configuration versus the default
  - healthcheck protocols (default or defined) versus service protocols

Raise an exception if a healthcheck URI is specified for a load
balancer healthcheck using any protocol other than HTTP.

Also adds tests for the above behaviour:

  - Add a spec test to ensure that the default URI for healthchecks
    using the HTTP protocol is '/'. The behaviour we are testing for was
    implemented in e9c524b42397121d232667ba29d6739bbba63091.

  - Add a spec test to ensure that the default URI for healthchecks
    using the HTTPS protocol is ''. The behaviour we are testing for was
    implemented in e9c524b42397121d232667ba29d6739bbba63091.

  - Add a spec test to ensure that the default URI for healthchecks
    using the TCP protocol, when the load balancer service protocol is
    'HTTP', is ''. The behaviour we are testing for was implemented in
    this same commit.

  - Add two spec tests that expect an exception to be raised if we
    attempt to define a healthcheck URI for a TCP or HTTPS healthcheck.
    Only HTTP healthchecks support a healthcheck URI. The behaviour we
    are testing for was implemented in this same commit.

[1]:
http://pubs.vmware.com/vcd-55/topic/com.vmware.vcloud.admin.doc_55/GUID-C12B3954-155F-48AF-9855-E0DE026752D0.html