Add schemas and includeSchema parameters to maven generateChangeLog

[MalloD12]

Impact

• Bug fix (non-breaking change which fixes expected existing functionality)
• Enhancement/New feature (adds functionality without impacting existing logic)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

schemas and includeSchema parameters have been added to LiquibaseGenerateChangeLogMojo class to let liquibase know which schemas needs to consider at the time of generating a change log, as well as whether to include schema names on it.

Fixes #3174

Things to be aware of

• Nothing

Things to worry about

• Nothing

Additional Context

N/A

[github-actions]

Unit Test Results

  4 620 files  ±0    4 620 suites  ±0   35m 20s ⏱️ - 2m 20s
  4 615 tests ±0    4 396 ✔️ ±0     219 💤 ±0  0 ❌ ±0 
54 552 runs  ±0  49 528 ✔️ ±0  5 024 💤 ±0  0 ❌ ±0 

Results for commit df2f0fe. ± Comparison against base commit cd2d6b0.

♻️ This comment has been updated with latest results.

[nvoxland]

Code review and test results:

Things to be aware of:

• Code changes are what I'd expect
• The maven diff (also does diffChangeLog) code already had the schemas attribute in it, so no need to update that

Things to worry about:

• Nothing

[FBurguer]

For this PR, I made the next few tests:

• includeSchema with true value should include schemaName attribute for each object: PASS

• includeSchema with true false should NOT include schemaName attribute for any object: PASS

• Not using includeSchema should have the same behavior as setting includeSchema on false: PASS

• schema includes all the objects from the specified schemas: PASS

• Not using schema parameter just sets the schema parameter as default schema (including schema parameter without any specified schema has the same behavior): PASS

This was tested with all 4 changelogs formats (xml, sql, json and yml)

Test Environment:
Java 8
Windows 10
Postgresql 13 container