Feat: add liquibase for database migrations

[tom-rm-meyer-ISST]

Description

solves #799

Adds

• liquibase dependency to pom
• liquibase migrations for
  • 3.1.0 schema as baseline
  • 3.2.0 schema as migration
• updated local deployment
  • to use liquibase migrations
  • by adding a liquibase dumper
• updated chart to only validate schema
• updated documentation

helm chart and version have already been up to date due to unpublished release.

Please note: around 2k alone are the baseline scheme autogenerated. As a committer, I don't see IP concerns even if the size is bigger than the average pr.

Pre-review checks

Please ensure to do as many of the following checks as possible, before asking for committer review:

• DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
• Copyright and license header are present on all affected files
• If helm chart has been changed, the chart version has been bumped to either next major, minor or patch level (compared to released chart).

[tom-rm-meyer-ISST]

raised ip lab issue for liquibase 4.32.0: https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/22467

Might downgrade if today is not sent out

[ReneSchroederLJ]

Overall great job. Just some minor details and some questions regarding the use of foreign keys.

[tom-rm-meyer-ISST]

helm test now works. Version has not been bumped as this version number is unreleased.

[ReneSchroederLJ]

LGTM. Thank you for your efforts. Great work

[mhellmeier]

I only see a possible problem in the >1k LOC changes and the failing pipeline. Since the first thing is argumented by the committer @tom-rm-meyer-ISST

Please note: around 2k alone are the baseline scheme autogenerated. As a committer, I don't see IP concerns even if the size is bigger than the average pr.

and the failed pipeline is related to the version change, I would approve.