Repository: quarkusio/quarkus
Issue: Hibernate reactive disregarding quarkus.hibernate-orm.jdbc.timezone

### Describe the bug

I have the last couple of days been trying to understand why my code does not consider `TIMESTAMP WITH TIME ZONE` in my main postgresSQL application that uses hibernate reactive so I created two smaller applications to test just test how hibernate-orm and hibernate-reactive work in quarkus with time zones.

First of I tried hibernate reactive and stumbled across the issue listed in #10768 on my own whilst running my `@QuarkusIntegrationTest` and `@QuarkusTest` and then changed my approach to use the normal “jdbc driver” to get flyway working to have it more like main PostgreSQL project. After the jdbc change I once of my test suits with `quarkus.hibernate-orm.jdbc.timezone` set to `UTC` with no effect whilst always running with `user.timezone=Etc/GMT-1` to simulate a consistent time zone, but neither of these settings helped ☹. So after that I created a `user.timezone=UTC` test which works since now both my postgres container and quarkus application now run in UTC. 

So then does it work in the normal quarkus hibernate-orm implementation? Well yeah everything works fine there when having `quarkus.hibernate-orm.jdbc.timezone` set to `UTC`.

P.S. One thing I forgot to comment about in my findings is the code that converts a `TIMESTAMP WITH TIME ZONE` from a database field (that is stored in postgres as UTC) to UTC again without taking into regard the time zone part of the original value in the database before converting it to the java object with the user.timezone so… the conversion loses one hour in my GmtIT.java tests… 👏🎉🧨😂. But this is releated to the other issue that has already been created.

P.S.S. Create a branch in the hibernate reactive application with no flyway.

### Expected behavior

quarkus.hibernate-orm.jdbc.timezone works according to specificaiton and can take into account database timezone when converting

### Actual behavior

Does nothing application boot timezone is used for all convertion of date and time

### How to Reproduce?

Github repos with my test code:
- [hibernate-reactive repo](https://github.com/agreedSkiing/test-hibernate-reactive-timezone-postgres)
- [hibernate-orm repo]( https://github.com/agreedSkiing/test-hibernate-timezone-postgres)

### Output of `uname -a` or `ver`

Linux DI-001000104447 4.19.128-microsoft-standard #1 SMP Tue Jun 23 12:58:10 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

### Output of `java -version`

java version "17.0.5" 2022-10-18 LTS Java(TM) SE Runtime Environment (build 17.0.5+9-LTS-191) Java HotSpot(TM) 64-Bit Server VM (build 17.0.5+9-LTS-191, mixed mode, sharing)

### GraalVM version (if different from Java)

_No response_

### Quarkus version or git rev

2.15.0.Final

### Build tool (ie. output of `mvnw --version` or `gradlew --version`)

Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)

### Additional information

_No response_

Changed files:
extensions/hibernate-reactive/deployment/src/main/java/io/quarkus/hibernate/reactive/deployment/HibernateReactiveProcessor.java

diff --git a/extensions/hibernate-reactive/deployment/src/main/java/io/quarkus/hibernate/reactive/deployment/HibernateReactiveProcessor.java b/extensions/hibernate-reactive/deployment/src/main/java/io/quarkus/hibernate/reactive/deployment/HibernateReactiveProcessor.java
index c5f5207fa3b..0fdcd1e39ab 100644
--- a/extensions/hibernate-reactive/deployment/src/main/java/io/quarkus/hibernate/reactive/deployment/HibernateReactiveProcessor.java
+++ b/extensions/hibernate-reactive/deployment/src/main/java/io/quarkus/hibernate/reactive/deployment/HibernateReactiveProcessor.java
@@ -310,6 +310,13 @@ private static ParsedPersistenceXmlDescriptor generateReactivePersistenceUnit(
                 String.valueOf(persistenceUnitConfig.query.inClauseParameterPadding));
 
         // JDBC
+        persistenceUnitConfig.jdbc.timezone.ifPresent(
+                timezone -> desc.getProperties().setProperty(AvailableSettings.JDBC_TIME_ZONE, timezone));
+
+        persistenceUnitConfig.jdbc.statementFetchSize.ifPresent(
+                fetchSize -> desc.getProperties().setProperty(AvailableSettings.STATEMENT_FETCH_SIZE,
+                        String.valueOf(fetchSize)));
+
         persistenceUnitConfig.jdbc.statementBatchSize.ifPresent(
                 statementBatchSize -> desc.getProperties().setProperty(AvailableSettings.STATEMENT_BATCH_SIZE,
                         String.valueOf(statementBatchSize)));