LIBCLOUD-625: Allow for internal GCE authorization with metadata service

This PR provides support for authorizing requests from within GCE directly by pulling an authorization token out of GCE's internal metadata services.  This greatly simplifies using libcloud inside GCE since it does not require the user to copy around private auth files.  The only parameter required for this method is the user's Project ID.  See the included docs for a sample use-case.

This PR also attempts to address https://issues.apache.org/jira/browse/LIBCLOUD-607 by appending the Project ID to the cached credential file.
Please use `libcloud.utils.connection.get_response_object` method. There is an example of how to use it at https://github.com/apache/libcloud/blob/trunk/libcloud/pricing.py#L203

This method uses Libcloud HTTP machinery underneath. Eventually, we will probably switch to the `requests` library, but now this is the way to go.