Relates tosquare/okhttp#3146. This was from#71.There is a draft PRhttps://github.com/square/okhttp/pull/7185/files which documents OkHttp's ideal handling of cancellation including interrupts.But a few key points1) This is a target state, and OkHttp does not currently handle interrupts correctly.  In the past this has been identified, and the advice is to avoid interrupts on Http threads, see discussion onsquare/okhttp#1902. Also an attempt at a fix heresquare/okhttp#7023 which wasn't in a form to land.2) Even with this fixed, it is likely to never be optimal, because of OkHttp sharing a socket connection for multiple inflight requests.Fromsquare/okhttp#7185```Thread.interrupt() is Clumsy----------------------------`Thread.interrupt()` is Java's built-in mechanism to cancel an in-flight `Thread`, regardless ofwhat work it's currently performing.We recommend against using `Thread.interrupt()` with OkHttp because it may disrupt shared resourcesincluding HTTP/2 connections and cache files. In particular, calling `Thread.interrupt()` may causeunrelated threads' call to fail with an `IOException`.```This PR leaves the Loader/DataSource thread parked on a countdown latch, while this may seem wasteful and an additional context switch. However in practice the response isn't returned until the Http2Connection and Http2Reader have a response from the server and these means effectively parking in a `wait()` statement herehttps://github.com/square/okhttp/blob/9e039e94123defbfd5f11dc64ae146c46b7230eb/okhttp/src/jvmMain/kotlin/okhttp3/internal/http2/Http2Stream.kt#L140PiperOrigin-RevId: 446652468

Relates tosquare/okhttp#3146. This was fromandroidx/media#71.There is a draft PRhttps://github.com/square/okhttp/pull/7185/files which documents OkHttp's ideal handling of cancellation including interrupts.But a few key points1) This is a target state, and OkHttp does not currently handle interrupts correctly.  In the past this has been identified, and the advice is to avoid interrupts on Http threads, see discussion onsquare/okhttp#1902. Also an attempt at a fix heresquare/okhttp#7023 which wasn't in a form to land.2) Even with this fixed, it is likely to never be optimal, because of OkHttp sharing a socket connection for multiple inflight requests.Fromsquare/okhttp#7185```Thread.interrupt() is Clumsy----------------------------`Thread.interrupt()` is Java's built-in mechanism to cancel an in-flight `Thread`, regardless ofwhat work it's currently performing.We recommend against using `Thread.interrupt()` with OkHttp because it may disrupt shared resourcesincluding HTTP/2 connections and cache files. In particular, calling `Thread.interrupt()` may causeunrelated threads' call to fail with an `IOException`.```This PR leaves the Loader/DataSource thread parked on a countdown latch, while this may seem wasteful and an additional context switch. However in practice the response isn't returned until the Http2Connection and Http2Reader have a response from the server and these means effectively parking in a `wait()` statement herehttps://github.com/square/okhttp/blob/9e039e94123defbfd5f11dc64ae146c46b7230eb/okhttp/src/jvmMain/kotlin/okhttp3/internal/http2/Http2Stream.kt#L140PiperOrigin-RevId: 446652468