Check for usage of javax.persistence configuration properties in Hibernate extensions

[Sanne]

Description

The current Hibernate ORM builds are lenient on configuration properties to be prefixed with either javax.persistence or jakarta.persistence; in most cases (it's not bullet-proof currently) the ORM will detect ambiguity and also log warnings, but such safeguards in upstream ORM aren't enough in Quarkus as we also need to handle implicitly set properties and the potential for these to be overriden.

Implementation ideas

We should be highly paranoid in accepting any javax.persistence, and check both:

• unsupported properties in applications.properties
• anything specified in a persistence.xml

Wondering about environment/system properties; I don't think they are affected but it might be worth checking - not remembering for sure.

At very least we shoul log a warning; wondering if we shouldn't fail outright - might actually be less tricky for end users to have a clear error rather than undefined behaviour.

[quarkus-bot]

/cc @gsmet (hibernate-orm), @yrodiere (hibernate-orm)