fix(orca-sql): Add migration for mariadb support

[juangod-wise]

This contribution was discussed in this slack thread:

https://spinnakerteam.slack.com/archives/C7J1CU4LA/p1722343931881969?thread_ts=1710447204.964799&cid=C7J1CU4LA

In summary:

The migration in 20201214-create-compressed-executions-table.yaml that is adding the column compression_type is not being ran for MariaDB because it contains dbms: mysql. This causes Orca to throw the following error on startup if using MariaDB:

liquibase.exception.DatabaseException: Unknown data type: 'COMPRESSION_TYPE_ENUM' [Failed SQL: (4161) ALTER TABLE spinnaker_orca.pipelines_compressed_executions ADD compression_type COMPRESSION_TYPE_ENUM DEFAULT 'ZLIB' NOT NULL

This happens because, since the column is not being created on that migration, the Postgres migration is ran because of this conditional:

orca/orca-sql/src/main/resources/db/changelog/20220427-add-compression-type-column-to-compressed-executions-tables-postgres.yaml

Lines 13 to 18 in ad53c17

	preConditions:
	onFail: MARK_RAN
	not:
	columnExists:
	tableName: pipelines_compressed_executions
	columnName: compression_type

And running the Postgres migration on MariaDB causes the error to appear. The solution for this is to create a new migration for MariaDB that is executed before the Postgres migration that adds the column only if using MariaDB. We can't change previous migrations because the changeset hash would change and would start failing for everyone who already applied it.

Spinnaker should be able to support MariaDB as there are mentions in the documentation:

https://spinnaker.io/docs/setup/productionize/persistence/orca-sql/#mariadb