HHH-14584 Allow PhysicalNamingStrategy implementations to detect when a name is implicit or explicit

[peter1123581321]

In HHH-14584, an additional field was requested in Identifier to indicate explicit namings of columns.
This would allow more possibilies in a custom PhysicalNamingStrategy.

As PhysicalNamingStrategy also provides methods for sequences and tables, this PR also implements handling explicit namings of both of them.
However, I did not provide it for schemas and catalogs.

Many thanks in advance for feedback, comments and change requests. :)

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license
and can be relicensed under the terms of the LGPL v2.1 license in the future at the maintainers' discretion.
For more information on licensing, please check here.

---

https://hibernate.atlassian.net/browse/HHH-14584

[yrodiere]

Hey @peter1123581321 , it looks like your PR isn't passing tests on all DBs. Also, since it's been a while (sorry) it's now conflicting with the main branch.

Could you please rebase, force push, and have a look at test results to see what needs fixing?

[peter1123581321]

@yrodiere Thanks for the reminder. Unfortunately, I haven't had any time lately. I've just rebased the branch and will have a look on the failed tests in the following days. :-)

[yrodiere]

Thanks for the update! A few comments below, though we mostly need to determine if the CI failures are real or not.

[peter1123581321]

@yrodiere thanks for the hint conerning getSequenceNextValString, everything's green now :-)

[yrodiere]

Thanks. I allowed Jenkins CI to start. Let's merge once that one is green!

[yrodiere]

We may have to delay this after all, because main is currently 7.2 in CR phase. See #11285 . But if we do, I will open a new PR with the same changeset, to be merged once main becomes 7.3.

[yrodiere]

New PR: #11297