`from google.cloud import logging` collides with `logging` from standard library

[busunkim96]

Also, an issue with from google.cloud import logging is that it collides with the logging standard library, and they are often going to be used together. Right now we tell users to import as import google.cloud.logging and use the full path in their code. I wonder if it would make sense to rename the library to google.cloud.cloudlogging or something so there's no naming conflict

Originally posted by @daniel-sanche in #83 (comment)

[daniel-sanche]

After getting some feedback, I'm going to hold off on this. We don't want to confuse existing customers more than needed