When Mobile Service returns in an UnHealthy state delete

[azurecoder]

When creating a new mobile service it can return in an unhealthy state - the most likely cause is that the database has not been created as part of the deployment workflow. If this occurs then check the state of the deployment and call delete.

[azurecoder]

updated this so that if the unhealthy state is returned then a db is delete - this may cause problems since if the server is not available or not returned from the service then it may not be possible to delete !! and may be blow up .. will fix if occurs and work around