Error handling / logging

A bunch of things going on here:

* Faraday middleware to facilitate logging of all requests/responses sent to the adapter
* Ability to capture errors that may occur on deployment creation and bubble them back up to the local agent
* Suppression of adapter errors that occur during `deployments#show` and `deployments#destroy`
* Global error handler for general error handling

[finishes #82690376]
Intentionally swallowing API errors on delete. If we have a situation where a service has already died, we don't want an error returned from the adapter to prevent us from cleaning up the deployment record in the database.