ISSUE-32936 | Allow plugging in Hibernate ORM's TypeContributor and FunctionContributor

[NickBeginner]

This PR fixes 32936

[quarkus-bot]

/cc @gsmet (hibernate-orm)

[yrodiere]

Note you'll need to update docs as well, to mention the new component types in that list:

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

Lines 543 to 561 in 206858a

	==== Plugging in other custom components
	The Quarkus extension for Hibernate ORM will automatically
	inject components annotated with `@PersistenceUnitExtension` into Hibernate Search.
	The annotation can optionally target a specific persistence unit with `@PersistenceUnitExtension(name = "nameOfYourPU")`.
	This feature is available for the following component types:
	`org.hibernate.Interceptor`::
	See <<interceptors>>.
	`org.hibernate.resource.jdbc.spi.StatementInspector`::
	See <<statement_inspectors>>.
	`org.hibernate.type.format.FormatMapper`::
	See <<json_xml_serialization_deserialization>>.
	`io.quarkus.hibernate.orm.runtime.tenant.TenantResolver`::
	See <<multitenancy>>.
	`io.quarkus.hibernate.orm.runtime.tenant.TenantConnectionResolver`::
	See <<programmatically-resolving-tenants-connections>>.

[NickBeginner]

@yrodiere i added the new components to the list, but i did not create the pages dedicate to them, is it okay or do you want me also to add the pages?

[yrodiere]

I think a section dedicated to "Custom functions and types" would make sense, so that it appears in the table of contents and people can easily find how to register those. But you probably don't need detailed explanation beyond one sentence and an example. Does that make sense?

[NickBeginner]

make perfect sense, gonna work on it this weekend. Thanks :)

[github-actions]

🎊 PR Preview 98dfb5a has been successfully built and deployed to https://quarkus-pr-main-51323-preview.surge.sh/version/main/guides/

• Images of blog posts older than 3 months are not available.
• Newsletters older than 3 months are not available.

[yrodiere]

Hey. You seem to be struggling with formatting -- do you know you can run a single command to have all the code formatted automatically?

./mvnw process-sources

See also https://github.com/quarkusio/quarkus/blob/main/CONTRIBUTING.md#ide-config-and-code-style

[quarkus-bot]

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit 11f1506.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

Warning

There are other workflow runs running, you probably need to wait for their status before merging.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 11f1506.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

---

Flaky tests - Develocity

⚙️ Maven Tests - JDK 21 Semeru

📦 integration-tests/devmode

❌ io.quarkus.test.devui.DevUIGrpcSmokeTest.testTestService - History

• Too many recursions, message not returned for id [1131135097] - java.lang.RuntimeException

java.lang.RuntimeException: Too many recursions, message not returned for id [1131135097]
	at io.quarkus.devui.tests.DevUIJsonRPCTest.objectResultFromJsonRPC(DevUIJsonRPCTest.java:175)
	at io.quarkus.devui.tests.DevUIJsonRPCTest.objectResultFromJsonRPC(DevUIJsonRPCTest.java:178)
	at io.quarkus.devui.tests.DevUIJsonRPCTest.objectResultFromJsonRPC(DevUIJsonRPCTest.java:178)
	at io.quarkus.devui.tests.DevUIJsonRPCTest.objectResultFromJsonRPC(DevUIJsonRPCTest.java:178)
	at io.quarkus.devui.tests.DevUIJsonRPCTest.objectResultFromJsonRPC(DevUIJsonRPCTest.java:178)
	at io.quarkus.devui.tests.DevUIJsonRPCTest.objectResultFromJsonRPC(DevUIJsonRPCTest.java:178)
	at io.quarkus.devui.tests.DevUIJsonRPCTest.objectResultFromJsonRPC(DevUIJsonRPCTest.java:178)

[yrodiere]

Thanks. Can you please add that section to the docs, then squash your commits?
After that I think we're good to merge :)

[yrodiere]

I think a section dedicated to "Custom functions and types" would make sense, so that it appears in the table of contents and people can easily find how to register those. But you probably don't need detailed explanation beyond one sentence and an example. Does that make sense?