use Hibernate's short-name mechanism to avoid exposing implementation classes

[NathanQingyangXu]

Hibernate has a Stragety mechanism (a little misleading for it refers to 'short-name' service, instead of Stragety Pattern) as examplified in Hibernate Integration Guide(https://docs.jboss.org/hibernate/orm/6.6/integrationguide/html_single/Hibernate_Integration_Guide.html) . As the doc explains:

Think of this as the short naming service. Historically to configure Hibernate users would often need to give fully-qualified name references to internal Hibernate classes. Of course, this has caused lots of problems as we refactor internal code and move these classes around into different package structures. Enter the concept of short-naming, using a well defined and well known short name for the strategy/implementation class.

It might be a good feature to our product with similar concern. The customization is based on the common ServiceLoader mechanism Hibernate mainly depends on (as an example stragety registration implementation in the doc).

This PR is not urgent (but given all other PRs were blocked by the first MQL translation PR (#27) due to integration testing verfication requirement), I created this DRAFT PR for you to consider.

[NathanQingyangXu]

close this PR for it is not urgent. Might open it when the PRs are not crowded later.