Allow renameColumn on newer SQLite versions

[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

Updated supports() method logic from RenameColumnGenerator class to return true for SQLite database from version 3.25 or higher, or any other supported database.

Fixes #2925

Things to be aware of

• Change method logic to consider SQLite DB version.
• This change only has impact on SQLite, for any other database it will keep behaving as of now.

Things to worry about

• This method might need to be revisited once again in a future if for a newer version this change is not again supported.

Additional Context

• Nothing.

[github-actions]

Unit Test Results

  4 668 files  ±0    4 668 suites  ±0   33m 15s ⏱️ + 2m 8s
  4 609 tests ±0    4 380 ✔️ ±0     229 💤 ±0  0 ❌ ±0 
54 516 runs  ±0  49 448 ✔️ ±0  5 068 💤 ±0  0 ❌ ±0 

Results for commit 12636b1. ± Comparison against base commit 3c94c98.

♻️ This comment has been updated with latest results.

[nvoxland]

Code review and test results:

Things to be aware of:

• Change is isolated to sqlite, and only for newer versions of sqlite
• Adds integration test for sqlite
• Functional tests are failing due to needed test changes not merged into master and is unrelated to this change
• Test-harness is failing on mssql due to datatbase not starting, but the sqlite one ran which should be all we need

Things to worry about:

• Nothing

[XDelphiGrl]

Versions of SQLite greater than 3.25 support renaming columns. This fix allows Liquibase to generate SQL for column renames for those newer versions. The logic for older versions of SQLite remains unchanged (does not allow for column renames).

• New integration test added to validate column rename.
• No additional testing required.

APPROVED