fix maven liquibase execution

[hide212131]

Fixes #19518

Issue fixes for the following problems:

• No specified version for h2.
• Outdated version of validator-api.
• master.xml cannot be detected because its path is not included in the classpath.
• defaultSchemaName is not passed to pom."

I have a slight concern about the reported vulnerabilities for all versions of h2 (which the vendor claims are not vulnerabilities). While I think it's not a problem since h2 is used only in development (not in production), it might impact the automatic version management in JHipster's pom (would writing it explicitly in pom.xml lead to frequent warnings?).

---

Please make sure the below checklist is followed for Pull Requests.

• All continuous integration tests are green
• Tests are added where necessary
• The JDL part is updated if necessary
• jhipster-online is updated if necessary
• Documentation is added/updated where necessary
• Coding Rules & Commit Guidelines as per our CONTRIBUTING.md document are followed

When you are still working on the PR, consider converting it to Draft (below reviewers) and adding skip-ci label, you can still see CI build result at your branch.

[hide212131]

Hmm... It's problematic that this issue keeps arising in every review going forward. Is there a good way to avoid this?

[mshima]

LGTM.
The dependency review should fail only at dependency introduction (this PR) following PRs should not fail anymore.
I am more concerned about sonar. If sonar pops a security issue we should try to whilelist or drop the fixed version.