Output "may lose settings" warning on mysql/mariadb for more impacted change types

[nvoxland]

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

MySQL/MariaDB's alter table ... modify column syntax requires a complete redefinition of the column when modifying a column, such as setting a comment, changing a datatype, etc.

The the setColumnRemarks, addDefaultValue, etc change does not support all possible column features, only the data type so anything else (like nullability etc) will be lost.

This PR expands the existing warning we had for modifyDataType, since that is all we can do for this.

Things to be aware of

• Only impacts Mysql/MariaDB.
• Adds warnings to addDefaultValue, setColumnRemarks, addNotNull, and dropNotNull changes.

Things to worry about

• Nothing

[github-actions]

Unit Test Results

  4 620 files  ±0    4 620 suites  ±0   32m 8s ⏱️ - 5m 31s
  4 594 tests ±0    4 379 ✔️ ±0     215 💤 ±0  0 ❌ ±0 
54 300 runs  ±0  49 280 ✔️ ±0  5 020 💤 ±0  0 ❌ ±0 

Results for commit 612ca9d. ± Comparison against base commit 65c65ba.

♻️ This comment has been updated with latest results.

[FBurguer]

For this PR tested if every change type listed before had a warning msg on MySQL and MariaDB:

• addDefaultValue
  MySQL: PASS
  MariaDB: PASS

• setColumnRemarks
  MySQL: PASS
  MariaDB: PASS

• addNotNull
  MySQL: PASS
  MariaDB: PASS

• dropNotNull
  MySQL: PASS
  MariaDB: PASS

  Test Environment:
  OS: Windows 10
  Java 8
  MySQL v8.0.27
  MariaDB v10.5