Verbose debug logs when Stackdriver returns an error response

[evandbrown]

When the nozzle interacts with Stackdriver to push metrics, the Stackdriver API may fail and return an error message that is not useful in diagnosing the problem. Considering the problem may lie with the request generated by the nozzle, the nozzle should dump verbose logs about the request and the nozzle's environment when it encounters an error from Stackdriver.

This is an example of the current state of logging provided by the nozzle when it encounters this situation:

rpc error: code = Internal desc = One or more TimeSeries could not be written: An internal error occurred.: timeSeries[3,8-10,13,21,22,35,37,40,47,51,58,69,71,82,91,95,100,101,115,117,133-135,138,155,162,169,173,178,179,181,182,186,187,190,199]