Google-pubsub: After upgrade of Quarkus to 2.12.0.CR1, there is an error in log (does not cause test failure)

I noticed, that the (mocked) tests for `google-pubsub` shows 3x following error in the log, which does not cause test failure - therefore it is not detected by the CI test runs:

```
SEVERE [io.grp.int.ManagedChannelOrphanWrapper] (Camel (camel-1) thread #4 - GooglePubsubConsumer[camel-quarkus-grouped-subscription-wuqs6084zxdeymnsbjrsanhh9deqhdcmuxzfwintahndnehcd]) *~*~*~ Channel ManagedChannelImpl{logId=33, target=localhost:49164} was not shutdown properly!!! ~*~*~*
Make sure to call shutdown()/shutdownNow() and wait until awaitTermination() returns true.: java.lang.RuntimeException: ManagedChannel allocation site
at io.grpc.internal.ManagedChannelOrphanWrapper$ManagedChannelReference.(ManagedChannelOrphanWrapper.java:93)
at io.grpc.internal.ManagedChannelOrphanWrapper.(ManagedChannelOrphanWrapper.java:53)
at io.grpc.internal.ManagedChannelOrphanWrapper.(ManagedChannelOrphanWrapper.java:44)
at io.grpc.internal.ManagedChannelImplBuilder.build(ManagedChannelImplBuilder.java:630)
at io.grpc.internal.AbstractManagedChannelImplBuilder.build(AbstractManagedChannelImplBuilder.java:297)
at org.apache.camel.component.google.pubsub.GooglePubsubComponent.getSubscriberStub(GooglePubsubComponent.java:209)
at org.apache.camel.component.google.pubsub.GooglePubsubConsumer$SubscriberWrapper.synchronousPull(GooglePubsubConsumer.java:170)
at org.apache.camel.component.google.pubsub.GooglePubsubConsumer$SubscriberWrapper.run(GooglePubsubConsumer.java:138)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
```

If you use camel-qauarkus before the quarkus upgrade (revision `b73c280fb906890e805a5b3976eba257724347b8`) and cherry-pick the new `googgle-pubsub` tests (revision `f4941aa9d6636030de98f515784502aad389360a`) into the code base, the error does not happen.

This is worth of more investigation, to be sure, that it can not affect users.