allow for multiple forwarding rules per load balancer.
NOTE address reflects only the last forwarding rule seen... dasein cant
yet cope with multiple addresses.
test if healthcheck is null before removing it. should address part of
bug 4772.
fix to disallow name change of Health checks which google does not allow
Throw exception on attempt to change HC name to prevent chaos downstream
more null checking to prevent mayhem
removed redundant addProviderLoadBalancerId that was causing timeouts.
another occurance of addProviderLoadBalancerId(loadBalancerName);
reversing last commit
Merge pull request #120 from unwin/2014.05

allow for multiple forwarding rules per load balancer.
NPE caught by labisso
extra null pointer testing, because can you really ever have too much
null testing? I dont think so, not when GCE is in play.

Also a little bit of lipstick...
try 2 at fixing the NPE labisso found
try #3
Merge pull request #122 from unwin/2014.05

NPE caught by labisso
added 3 null tests to help devine the true nature of the NPE being thrown from:
  ForwardingRuleList result = gce.forwardingRules().list(ctx.getAccountNumber(), ctx.getRegionId()).execute();
Merge pull request #127 from unwin/2014.05

added 3 null tests to help devine the true nature of the NPE being throw...
Merge pull request #128 from unwin/2014.05

was not populating the available zones for LoadBalancer object.
Merge pull request #131 from unwin/2014.05

2014.05
Merge pull request #133 from unwin/2014.05

BUG 4367 This allows for custom images to be removed.
[maven-release-plugin] prepare release dasein-cloud-google-2014.05.21