Move Hibernate ORM/Reactive configuration reference to the bottom of the guides

Because:

1. It's super long, it makes no sense to have it in the middle of the
   guide.
2. Other guides follow this approach as well, so we'd better be
   consistent.

Author: yrodiere

docs/src/main/asciidoc/hibernate-orm.adoc

@@ -100,7 +100,7 @@ They will often map to Hibernate ORM configuration properties but could have dif
 
 Also, Quarkus will set many Hibernate ORM configuration settings automatically, and will often use more modern defaults.
 
-For a list of the items that you can set in `{config-file}`, see <<hibernate-configuration-properties,Hibernate ORM configuration properties>>.
+For a list of the items that you can set in `{config-file}`, see <<configuration-reference>>.
 
 An `EntityManagerFactory` will be created based on the Quarkus `datasource` configuration as long as the Hibernate ORM extension is listed among your project dependencies.
 
@@ -295,9 +295,7 @@ There are no required properties, as long as a default datasource is configured.
 When no property is set, Quarkus can typically infer everything it needs to set up Hibernate ORM
 and will have it use the default datasource.
 
-The configuration properties listed here allow you to override such defaults, and customize and tune various aspects.
-
-include::{generated-dir}/config/quarkus-hibernate-orm.adoc[opts=optional, leveloffset=+2]
+The configuration properties listed in <<configuration-reference>> allow you to override such defaults, and customize and tune various aspects.
 
 [NOTE]
 ====
@@ -961,7 +959,7 @@ quarkus.hibernate-orm."offline".dialect.mariadb.bytes-per-character=1
 quarkus.hibernate-orm."offline".dialect.mariadb.no-backslash-escapes=true
 ----
 
-Refer to the <<hibernate-configuration-properties,Hibernate ORM configuration properties>> section for more details on the available properties.
+Refer to the <<configuration-reference>> section for more details on the available properties.
 
 
 [[caching]]
@@ -1949,3 +1947,8 @@ to learn more about the `dataStore` attribute.
 Please refer to the corresponding https://hibernate.org/repositories/[Hibernate Data Repositories]
 and https://jakarta.ee/specifications/data/1.0/jakarta-data-1.0[Jakarta Data]
 guides to learn what else they have to offer.
+
+[[configuration-reference]]
+== Configuration Reference for Hibernate ORM
+
+include::{generated-dir}/config/quarkus-hibernate-orm.adoc[opts=optional, leveloffset=+2]

docs/src/main/asciidoc/hibernate-reactive.adoc

@@ -116,7 +116,7 @@ Blocking (non-reactive) and reactive configuration xref:orm-and-reactive-extensi
 
 WARNING: Configuring Hibernate Reactive using the standard `persistence.xml` configuration file is not supported.
 
-See section <<hr-configuration-properties,Hibernate Reactive configuration properties>> for the list of properties you can set in `{config-file}`.
+See section <<configuration-reference>> for the list of properties you can set in `{config-file}`.
 
 A `Mutiny.SessionFactory` will be created based on the Quarkus `datasource` configuration as long as the Hibernate Reactive extension is listed among your project dependencies.
 
@@ -193,11 +193,9 @@ and will have it use the default datasource.
 
 The configuration properties listed here allow you to override such defaults, and customize and tune various aspects.
 
-Hibernate Reactive uses the same properties you would use for Hibernate ORM. You will notice that some properties
+Hibernate Reactive uses the same properties you would use for Hibernate ORM: see <<configuration-reference>>. You will notice that some properties
 contain `jdbc` in the name but there is no JDBC in Hibernate Reactive, these are simply legacy property names.
 
-include::{generated-dir}/config/quarkus-hibernate-orm.adoc[opts=optional, leveloffset=+2]
-
 [TIP]
 ====
 Want to start a PostgreSQL server on the side with Docker?
@@ -446,3 +444,8 @@ by providing active record style entities (and repositories) and focuses on maki
 To find out more on how the <<quarkus-hibernate-orm_quarkus-hibernate-orm-validation-mode,`quarkus.hibernate-orm.validation.mode` configuration property>>.
 influence your Hibernate Reactive application see the xref:hibernate-orm.adoc#validator_integration[corresponding Hibernate ORM guide],
 as these modes work the same in both cases.
+
+[[configuration-reference]]
+== Configuration Reference for Hibernate Reactive
+
+include::{generated-dir}/config/quarkus-hibernate-orm.adoc[opts=optional, leveloffset=+2]