Kamon looses context when http4s client raises an exception

[matwojcik]

If the http4s client raises an exception - e.g. when e.g. java.util.concurrent.TimeoutException is raised after setting connection timeout:

BlazeClientBuilder[F]
      .withRequestTimeout(100.millis)

then it seems that kamon context is lost, and e.g. traceId is not propagated to MDC for logging.

If there is not any exception but a request ending with e.g. 500, then it seems to be working fine.