While the Kotlin layer itself doesn't change depending on the flavor
(normal or lite), the underlying Java generated library does. This
effectively just selects either a `java_lite_proto_library` or a
`java_proto_library` depending on the flavor, everything else remains
the same.

… cancelled it's handled in `sender` coroutine (lines 311-319). Both client call cancellation (line 316) and failure propagation (line 317) eventually reach the listener `onClose` callback (where `responses` flow is closed), but which one reaches the place first is racy. When failure propagation reaches the callback first, the flow is cancelled with cancellation exception (expected). But if the client call cancel reaches the callback first, the flow is cancelled with GRPC status exception (unexpected). This change recovers the cancellation from GRPC status exception if it was the cause to make the behavior deterministic and aligned with expectations. I don't know how to test this change reliably. I succeeded to reproduce the issue via slow emulator tests only with some chance over 100+ runs.

…`installDist` task with Java 8 on my ARM based M1 Mac.

These names are chosen to mirror the action mnemonics in the
kt_jvm_grpc_library implementation.

…ava and Kotlin sources.

Subsequently, configure ktlint to avoid checking generated directories as a whole.

* version bumps

* add test retry

* bump coroutines

…erceptors (#400)

* prepare 1.3.1 release and bump example deps

* bump examples testing to jdk17