[Maintenance]Run schema validation on mysql pipeline

[Ferror]

Q	A
Branch?	master
Bug fix?	no
New feature?	no
BC breaks?	no
Deprecations?	no
Related tickets	PR
License	MIT

The PR should be failing, but after the #13846 it should be nice and green :)

This is what happened here. Cherry-pick the change from #13846 that all database pipelines were failing. What I found is that we actually test the schema, but accept failing steps. By not accepting that we were able to find out the problem with some extra things. Like our PostgreSQL schema is successfully validated, but our MariaDB schema is not. That's because of JSON type and the difference between MySQL and MariaDB. Now we have to decide whether we want these two schemas to be up to date or we turn off migrations on MariaDB

[Ferror]

@lchrusciel ready

[lchrusciel]

Hey Zbychu,

can you cherry-pick #13846 commit to your work, so we can merge it all together and check the correctness of the solution?

[Ferror]

We dont need to specify that as of https://www.doctrine-project.org/projects/doctrine-dbal/en/latest/reference/configuration.html#automatic-platform-version-detection

[lchrusciel]

The base of this pull-request was changed, you need fetch and reset your local branch
if you want to add new commits to this pull request. Reset before you pull, else commits
may become messed-up.

Unless you added new commits (to this branch) locally that you did not push yet,
execute git fetch origin && git reset "pipeline-schema-validate" to update your local branch.

Feel free to ask for assistance when you get stuck 👍

[lchrusciel]

I've switched to 1.11 to fix existing release with patch