Fix for Bug 4772 after seeing enhanced debug output it was determined
that description, host, and requestPath are optional for GCE.
massive null checking enhancements chasing Bug 4775
return null for LoadBalancerHealthCheck's that are bogus.
massive sanitization added to toLoadBalancerHealthCheck()
Now copes with HealthChecks that only have names.

hc.getPort was returning null, which freaked out
LoadBalancerHealthCheck.getInstance()
Merge pull request #116 from unwin/2014.05

Fix for Bug 4772 after seeing enhanced debug output it was determined
Updated to not assume forwarding rules are named the same as load
balancers.  now looks up forwarding rule actually attached to the load
balancer(TargetPool)
Merge pull request #118 from unwin/2014.05

Updated to not assume forwarding rules are named the same as load
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