Initial Data Model for Schema SQL Generation that can generate SQL for a simple entity.

Closes #1478

…ween current and previous state

… deletions.

…s own class

…SchemaModel

…rform any difference/comparison)

…bles / columns (i.e. only perform additions - unless the user implements a predicate telling us otherwise)

…en querying DB state is the Reference Name.

…bsolute file name

… ones

Reformat code, switch to tabs. Accept property in DatabaseTypeMapping to provide more context to the type mapping component.

Rename LiquibaseChangeSetGenerator to …Writer as we're writing a changeset and computing the contents is a consequence of writing a changeset. Refine naming to express what we're actually doing.

Introduce setters for enhanced configuration of predicates. Reduce visibility of types to avoid unwanted public API where public access is not needed.

Remove usused code, move methods around for improved grouping of code.

Rename package to schema as the schema is being created and updated and not generated. Rename …Model classes to just their name as types are package-private and not visible externally. Refactor SchemaDiff to Java record.

Use different overloads to write schema changes to avoid LiquibaseException leaking into cases where no diff is being used. Introduce SchemaFilter to filter unwanted mapped entities.

Add tests for changeset-creation.

Move code to JDBC module. Introduce comparator strategy to customize how table and column names are compared.