Client exceptions not recorded in metrics

Metrics [are recorded by the ClientMetricInterceptor](https://github.com/cashapp/misk/blob/master/misk/src/main/kotlin/misk/client/ClientMetricsInterceptor.kt#L26-L35). The ClientMetricInterceptor records the duration of actions. It annotates them with an action name and the result.

Recently, I had an experience where I was looking to understand the impact of a downstream service's outage. I looked at the metrics. There was no record of the outage in the gRPC client metrics. After some further investigation, I found logs that showed the gRPC client was throwing exceptions. The reason these exceptions weren't recorded was because the only exception that misk makes available as a metric is an `SocketTimeoutException`.

Why not record metrics for any exceptional circumstance? Given that there are already some kinds of errors, it feels like common sense to include these ones too. It would improve visibility and help us understand our systems.

Start with misk/src/main/kotlin/misk/client/ClientMetricsInterceptor.kt, especially the referenced lines, and trace how client action duration, action name, result, and SocketTimeoutException are handled. Confirm the current behavior for other exceptional circumstances and identify the relevant metric expectations. Done means exceptional client failures are represented in the gRPC client metrics so downstream outages are visible.

Written by the indexing model from the issue text.