User code GRPC context cancellation propagates to driver level

[zdazzy]

The driver uses connection pooling by default. Each connection is a long-living bidirectional GRPC stream. When a user GRPC request completes it cancels its context at the end, which in turn causes the underlying session to be cancelled as well. This in turn causes the subsequent DB request to fail with BAD_SESSION code.

Using an abstraction layer in a form of JDBC (not to mention other layers like spring-data-jdbc) makes it impossible to mitigate this behavior without resorting to some nasty crutch code.

Some form of control over this would be appreciated. Maybe in a form of a JDBC property for the driver.