Resolve "Create a new table to track schema inconsistencies"

What does this MR do and why?

Add a new table to store database schema inconsistencies for GitLab

Migration output:

up:

main: == 20230307132729 CreateSchemaInconsistencies: migrating ======================
main: -- create_table(:schema_inconsistencies)
main: -- quote_column_name(:object_name)
main:    -> 0.0000s
main: -- quote_column_name(:table_name)
main:    -> 0.0000s
main: -- quote_column_name(:valitador_name)
main:    -> 0.0000s
main:    -> 0.0084s
main: == 20230307132729 CreateSchemaInconsistencies: migrated (0.1199s) =============

down:

main: == 20230307132729 CreateSchemaInconsistencies: reverting ======================
main: -- drop_table(:schema_inconsistencies)
main:    -> 0.0024s
main: == 20230307132729 CreateSchemaInconsistencies: reverted (0.0072s) =============

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

Related to #394824 (closed)