fix(supported-version): model MariaDB as a separate service from MySQL

[rhoerr]

Summary

Fixes the 2.4.9 setup-install CI failure reported in #365 by promoting MariaDB to its own first-class service in the matrix schema, mirroring the existing opensearch/elasticsearch and valkey/redis patterns. This is @damienwebdev's preferred approach from the issue thread (closing the alternate single-template fix from #366).

Why the obvious one-template fix doesn't work

The mariadb:11.4 image used for Magento 2.4.9 no longer ships mysqladmin, so the existing health command --health-cmd="mysqladmin ping" exits non-zero forever and GitHub Actions tears the job down at Initialize containers. The MariaDB-recommended replacement, healthcheck.sh --connect --innodb_initialized, ships in MariaDB images but not in mysql:8.4, which 2.4.6-p15 / 2.4.7-p10 / 2.4.8-p5 still use. A single template can't cover both engines, so each needs its own.

What changed — supported-version

Area	Change
supported-version/src/matrix/matrix-type.ts	Added mariadb: string to PackageMatrixVersion
supported-version/src/services/service-config.ts	Added mariadbConfig template using healthcheck.sh --connect --innodb_initialized. mysqlConfig is unchanged.
supported-version/src/services/build-services.ts	New getDatabaseChoice() helper (mariadb preferred over mysql), branches the emitted service key
supported-version/src/versions/**/*.json	22 entries that encoded MariaDB by stuffing the image into the mysql field now use a top-level mariadb key
supported-version/src/services/build-services.spec.ts	6 new database-selection tests
supported-version/src/nightly/amend-matrix-for-next.spec.ts	Fixtures gain mariadb: "" to satisfy the new required field
.github/workflows/integration.yaml	Port lookup falls back: job.services.mysql.ports['3306'] || job.services.mariadb.ports['3306']
supported-version/README.md	include_services description mentions MariaDB
supported-version/dist/index.js	Rebuilt

What changed — setup-install

The companion install action also needs to understand the new key, since matrix lanes whose database is MariaDB now emit services.mariadb:

Area	Change
setup-install/src/build-command.ts	Added mariadb? to the Services interface; new getDatabaseService() helper (mariadb preferred) feeds the --db-host / --db-name / --db-user / --db-password flags
setup-install/src/index.ts	The pre-install SET GLOBAL log_bin_trust_function_creators = 1; prep call routes through the same helper (the SQL and mysql CLI both work against MariaDB)
setup-install/src/build-command.spec.ts	New mariadb-only and mariadb-preferred-over-mysql cases
setup-install/dist/index.js	Rebuilt

⚠️ Breaking change for matrix consumers

GitHub Actions exposes each service container under a DNS alias that equals the map key in the services: block. With this change, any matrix lane whose database is MariaDB now emits services.mariadb instead of services.mysql. That affects:

• Magento Open Source: the >=2.4.7 <2.4.8 range, the >=2.4.9 <2.4.10 range, the bare default and :next aliases, plus the individual entries 2.4.7 through 2.4.7-p10 and 2.4.9.
• Mage-OS: >=1.0 <1.1 range, plus the individual entries 1.0.2 through 1.0.6.

Downstream workflows that reference job.services.mysql.* or that connect to host mysql from a job container will not resolve on those lanes. Two fixes for consumers:

# Option A: fallback expression (one-line edit; same pattern used internally here)
--port ${{ job.services.mysql.ports['3306'] || job.services.mariadb.ports['3306'] }}

# Option B: read the engine choice from the matrix entry directly
${{ matrix.mariadb && 'mariadb' || 'mysql' }}

Internal consumers in this repo are covered:

• setup-install now accepts either service key (this PR)
• setup-magento and warden/setup-environment already connect through db / 127.0.0.1 rather than the service-key alias
• integration.yaml line 77 uses Option A above

Local build & test results

supported-version

$ npx jest
Test Suites: 12 passed, 12 total
Tests:       117 passed, 117 total
Snapshots:   0 total
Time:        1.136 s

$ npm run build
> npx esbuild --outfile=dist/index.js --platform=node --bundle --minify src/index.ts
  dist/index.js  497.1kb
⚡ Done in 13ms

setup-install

$ npx jest
Test Suites: 1 passed, 1 total
Tests:       18 passed, 18 total
Snapshots:   0 total
Time:        0.504 s

$ npm run build
> npx esbuild --outfile=dist/index.js --platform=node --bundle --minify src/index.ts
  dist/index.js  447.9kb
⚡ Done in 13ms

Test plan (CI)

• CI setup-install (magento/project-community-edition:2.4.9) lane reaches Initialize containers successfully
• CI setup-install (magento/project-community-edition:2.4.8-p5) lane still passes (confirms mysqladmin ping template still works for mysql-image lanes)
• Spot-check generated matrix JSON for one mariadb lane and one mysql lane to confirm the service key (mariadb vs mysql) and health command

Fixes #365

🤖 Generated with Claude Code