[core] Deprecate Fog::Connection

This reapplies the deprecation warnings that were originally part of
7ee3535 when using Fog::Connection request.

Unfortunately the Mock world does not exercise any of the code affected
by this change so I missed that I had adjusted the signature of the
method.

If you pass a parser argument into Fog::Connection you should switch to
using Fog::XML::SAXParserConnection and pass the parser as the first
argument to `#request`

If you don't it is better to use Fog::Core::Connection to get rid of the
backwards compatibility code and XML dependency.

This will make fog VERY NOISY since you'll get output for every request
on out of date services.
[GH-2711] Add Fog::XML::Connection

Attempting to move to using Fog::XML::SAXParserConnection directly
failed because the arguments changed.

This adds another compatibility level with two key differences:

1) It's namespaced within XML so stands out as not being part of core
2) It is NOT creating deprecation warnings so can be used as the final
   step if rewriting to use SAXParserConnection is undesired

So when merged Fog::Connection usage will create noise.

Fog::XML::Connection works the same way and will be extracted to
"fog/xml" when we get to it.

Fog::Core::Connection just wraps Excon.request and leaves the response
body parsing to the provider.
[GH-2711] Replace Fog::Connection with XML shim

Unlike last attempt this replaces Fog::Connection with
Fog::XML::Connection which should be directly compatible.

Fog::Connection is there for old PRs but should be removed real soon.

Providers using JSON should be able to replace "XML" with "Core" within
their code to cut down on the dependency.

If I get the time I may attempt to clean up some but testing with Mock
will mean that is mostly educated guesswork.
initial commit of changes to add network interface during instance creation
Make Coveralls opt-in

Due to looking for a value of 'false' whenever I run tests locally
without the `COVERAGE` env variable coverage is very slowly, still
calculated - it then aborts without doing anything because I'm not using
a CI setup.

This adds the setting in for Travis to opt in and should exclude
coverage work for anyone running tests locally.
Reduce size of Travis matrix

We excluded almost as much as we care about and adding COVERAGE created
a number of invalid combinations so this changes the matrix to include
the workable combinations of Ruby version and Gemfile.

COVERAGE is only on Ruby 1.9.3 whilst I confirm this is working
Revert to original .travis.yml and include one case
[Brightbox] Add support for Cloud SQL service

This adds support for Brightbox's Cloud SQL DBaaS.

It is currently still part of the Compute service so all resources can
be managed from one connection to the service.
Update Flavours.rb with new M3 Instance Types

*Accouncement*: http://aws.typepad.com/aws/2014/01/aws-update-new-m3-features-reduced-ebs-prices-reduced-s3-prices.html
*Instance Types*: http://aws.amazon.com/ec2/instance-types/
[vcloud_director] fix typo as per #2621
[Brightbox] Remove old #destroy request

All the "destroy" methods were renamed to "delete" but this file was not
removed.
[openstack] image.update_image_members expects are incorrect #2627
[openstack] Fix for OpenStack flavor id calculation.
Use case-insensitive header access for Location.
Fix case sensitivity of the Content-type header.
make sure mock creates interface that doesn't already exist
[Docker] fixed attributes aliases
Merge branch 'AWS-run_instance-attach-network-interfaces' of github.com:madAndroid/fog into AWS-run_instance-attach-network-interfaces
Merge pull request #2716 from engineyard/firewall-in-use

[aws/security_group] update mock search and revoke
Merge pull request #2664 from mmatuska/vsphere_fix_nic_detection

[vsphere] fix broken detection of existing network interface type