ci: give each quibble job the dependencies and database it needs

[lens0021]

Not stacked on #468 — this stands on main on its own, and #468 wants it underneath rather than on top. See "Order" below.

What was wrong

femiwiki/quibble-action resolves what to clone from the first source that answers: the dependencies input, then extension.json's requires, then .phan/config.php's directory list. wikven names no extensions in requires, so the phan config was the source in use — which made one file answer two questions that have different answers:

• phan wants the directories whose symbols this code reaches for.
• the wiki wants whatever will not load without it.

Translate is both. UniversalLanguageSelector is only the second, and it was missing. So naming Translate for phan's benefit handed it to the installer too, and the installer refused it:

Error: A dependency error was encountered while installing the extension "Translate":
Could not find the registration file for the extension "UniversalLanguageSelector"

Translate itself confirms these are different lists: its .phan/config.php names AbuseFilter, AdminLinks, cldr, Echo, Elastica, Scribunto and TranslationNotifications — the optional integrations it reaches for — and does not name ULS, its one hard requires.extensions dependency.

Two lists, one per job

The install list moves to quibble.yml, where someone looking for "what does CI install" would look, and .phan/config.php is left alone to be about phan. Each job then gets the list it actually needs:

PHAN_DEPENDENCIES: Gadgets Translate
WIKI_DEPENDENCIES: Gadgets Translate UniversalLanguageSelector

Wikimedia splits this the same way and for the same reason — zuul/dependencies.yaml against zuul/phan_dependencies.yaml, chosen by whether the job name carries -phan, with parameter_functions.py recursing over the first and never the second ("since for Phan we never processed them recursively"). Their two entries for Translate share two of the ten names between them.

What is not copied is the mechanism. Wikimedia needs two maps because its dependency data lives away from the job definition and a job cannot pass its own list; a workflow job is written where its list is written, so a value per job is enough and the action needs no second input.

Naming the input also settles the resolution order: an extensions entry appearing in extension.json would otherwise take the phan config's place silently, and Gadgets/Translate would stop being cloned with nothing said.

The database

Quibble installs on MySQL unless told otherwise, and wikven never runs there — bin/build.php installs with --dbtype sqlite, and maintenance/build.php carries paths that exist only under it (one writer at a time, a database file per pass, SQLITE_BUSY). So the job with the extensions installed was standing on a backend the product does not use, while the phpunit jobs stood on the right backend without the extensions. Neither was where wikven runs. db: sqlite makes coverage the one that is.

The pin moves to an unreleased main commit because no release carries the db input yet. A composite action answers an undeclared input with a warning rather than an error, so a move back to v2.0.2 would leave the line reading as though it does something while the wiki quietly returned to MySQL — noted in the workflow for whoever reviews the dependabot pull request that offers exactly that.

The test

Installing Translate makes the handler in IndexerTest reach the real lookup, which asks the database whether the page above the one under test is marked for translation — and the test had not asked for a database, so it errored with RuntimeException: Database backend disabled.

The contract holds either way: absent, Translate cannot report a translation page; installed, a page nobody marked is not one. So the test asks for a database, and is named after the contract instead of after one of the two environments. MediaWikiGroupValidator::isTestInDatabaseGroup() matches @group Database against the class doc comment and nothing else, so it is declared there.

Both sides stay exercised, because the jobs differ in what they install: the quibble jobs bring Translate along, the phpunit jobs install MediaWiki alone.

Where CI stands now

job	database	extensions	MediaWiki
phpunit	SQLite	none	REL1_46 + master
coverage	SQLite	Gadgets, Translate, ULS	master
phan	—	Gadgets, Translate	REL1_46 + master

Order

This wants to land before #468, not after:

• On main today .phan/config.php names only Gadgets, so phan does not parse Translate and test: let phan see Translate instead of looking away from it #468's suppressions are still live and still used — phan stays green with this merged.
• With the install list explicit, test: let phan see Translate instead of looking away from it #468 becomes a pure static-analysis change: naming Translate in the phan config no longer moves what CI installs, so its coverage job goes green.

Merging this first turns #468 green without #468 having to change.