DBI-829: Expand tested MariaDB version range in CI

[pfcoperez]

This PR expands the pseudo-DSL within flow.yml used to described test matrix cases by allowing an optional row field that overrides the tag described by version-configs when present. e.g:

• Traditional entry: {pg: 18, mysql-flavor: 'maria-pos', mongo: '8.0', ch: 'latest'},, falling back to using:

              mysql-pos:
                img: 'mysql'
                tag: '5.7'
                env: ['MYSQL_ROOT_PASSWORD=cipass']
                parameters: ['--log_bin=mysql-bin', '--server-id=1', '--bind-address=::']

• Entry with parametrized tag: {pg: 18, mysql-flavor: 'maria-gtid', mysql-tag: '12-ubi', mongo: '8.0', ch: 'stable'},

Then it uses this mechanism to add the cases for MariaDB 12 and 13:

          {pg: 18, mysql-flavor: 'maria-gtid', mysql-tag: '12-ubi', mongo: '8.0', ch: 'stable'},
          {pg: 18, mysql-flavor: 'maria-gtid', mysql-tag: '13-ubi', mongo: '8.0', ch: 'stable'},

[dtunikov]

hm
i think we don't allow mariadb with file pos, do we?

[dtunikov]

i mean, i see that we already have it in the code
but i'm not sure why

[codecov]

⚠️ JUnit XML file not found

The CLI was unable to find any JUnit XML files to upload.
For more help, visit our troubleshooting guide.

[claude]

Code review

No issues found. Checked for bugs and CLAUDE.md compliance.

[github-actions]

❌ Test Failure

Analysis: The job failed deterministically because the CI matrix references a non-existent Docker image tag (mariadb:13-ubi → "manifest unknown"), a real config bug on the mariadb-extended-versions branch, not a flaky test.
Confidence: 0.97

⚠️ This appears to be a real bug - manual intervention needed

View workflow run

[pfcoperez]

Superseded by #4510