Upgraded to the jdk client version 0.10.0

[domaspoliakas]

Hello!

I hope it's ok to open a PR directly without an issue first.

This PR upgrades the http4s jdk client to 0.7.0. 0.7.0 is not binary-compatible with 0.5.0, so this is necessary if the downstream users (me 😄 ) wish to upgrade the jdk client.

I couldn't run tests because I don't have minikube set up. I'm hoping CI will catch anything that could be a problem, although the changes themselves are very straightforward.

Let me know if there's anything else that needs to be done!

[joan38]

Hi! Thanks for submitting a PR!
Looks like it's failing.

[domaspoliakas]

Thanks for that! I'll see if I can get minikube set up and debug these issues.

[joan38]

Tests failing with 0.9.1, maybe related to http4s/http4s-jdk-http-client#116

[yurique]

I added this pipe to the ws connection streams to deal with the IOExceptions:

  private def skipConnectionClosedErrors: Pipe[F, WSDataFrame, WSDataFrame] =
    _.map(_.some)
      .recover {
        // Need to handle (and ignore) this exception
        //
        // Because of the "conflict" between the http4s WS client and
        // the underlying JDK WS client (which are both high-level clients)
        // an extra "Close" frame gets sent to the server, potentially
        // after the TCP connection is closed, which causes this exception.
        //
        // This will be solved in a later version of the http4s (core or jdk).
        case e: java.io.IOException if e.getMessage == "closed output" => none
      }
      .unNone

Also changed the return type of the PodsApi#execStream from this:

Resource[F, F[Stream[F, Either[ExecStream, ErrorOrStatus]]]]

to this:

Stream[F, Either[ExecStream, ErrorOrStatus]]

pod tests passed locally for me