What does currentCoroutineContext().ensureActive() change when a catch-all is wrapped in a consumer timeout? This sandbox runs three versions of the same catch block against the cases a Kafka consumer actually meets.
// 1. original: swallows everything
try { call() } catch (ex: Throwable) { log(ex) }
// 2. type check
try { call() } catch (ex: CancellationException) { throw ex } catch (ex: Throwable) { log(ex) }