fix(deps): the dev dependency on core declares a range instead of anything

[rodrigoteamx]

milpa/core sat in require-dev as * — a constraint that admits 1.0, 2.0 and every major after them, whose contract this package has never seen. The family writes >=X <1.0; thirteen siblings already do, and this is one of seven still saying *.

Nothing moves to require, and that is the measured answer. src imports nothing from milpa/* at all: its nine files contain zero use statements — positive control on the same grep, nine namespace lines — and the only non-Milpa\Data symbol anywhere in src or tests is a {@see \Milpa\Live\Contracts\Component\ListsComponents} cross-reference inside the prose of a PagesResults docblock. That one nearly read as a hidden dependency; the generated docs settle it: the family generator leaves every {@see} unrendered, this package's own {@see RepositoryInterface} included, so the tag links nothing and requires nothing.

The single consumer of milpa/core here is tools/gen-docs.php, which runs the family generator (Milpa\Docs\SiteGenerator) shipped inside core's dist — dev-only tooling, and the reason autoload-dev maps Milpa\Docs\ into vendor/milpa/core/tools/gen-docs/.

The floor is measured, not assumed. With core pinned to v0.6.2 the generator still produced its 10 pages, and it does the same on v0.12.0 — so >=0.6.2 <1.0 is a range this package has actually been run against at both ends, and it is the floor agent, container, devtools, http, ops, resolver and workflow already declare.

	before (* → v0.12.0)	after (>=0.6.2 <1.0 → v0.12.0)
PHPUnit	120 tests / 233 assertions, 28 skipped	120 tests / 233 assertions, 28 skipped
PHPStan src	no errors	no errors
composer validate --strict	valid	valid
gen-docs	10 pages	10 pages (also 10 on core v0.6.2)

The 28 skips are local only — they are MysqlRepository's integration tests, and CI runs the MySQL 8.0 service that unskips them.

Closes a residue greenhouse evidence/0571 recorded.