test(compat): map post-12.0.0b5 pylance releases to lance-namespace 0.11

[amunra]

Backports one slice of upstream lance-format#8903 (1391e6cb7), "build(deps)!: bump lance-namespace to 0.11.1 across Java and Python". In that PR's words:

The compat harness also gains a tier in its namespace pin map, which tells it what lance-namespace range to install alongside each published pylance release. Releases cut after 12.0.0b5 will carry the new >=0.11.1,<0.12 range, so the map needs an entry for them; 12.0.0b5 and earlier keep the old one.

That tier is what this takes, unchanged, along with the three parameterised cases upstream added to pin the boundary either side of 12.0.0b5.

It is needed here because the harness discovers its version matrix at collection time rather than pinning it, taking the newest beta from the fury index. Once upstream published pylance 12.0.0-beta.6 — the first release carrying the new range — the harness kept asking pip for pylance==12.0.0b6 together with lance-namespace>=0.8.0,<0.9, which cannot resolve. The install failed before any Lance code ran, erroring every test parameterised on that version. Because the matrix is discovered rather than pinned, that broke every branch at once, not only ones touching Python.

No production code: both files are test-harness only, and this fork's own lance-namespace pin stays at >=0.8.5,<0.9. The map only decides what to install into the throwaway venv built for some other published pylance release.

Testing

Compat suite on this branch: 278 passed, 9 skipped, none failed — against 30 failed, 245 passed, 9 skipped before. The 31 12.0.0b6 cases now execute rather than erroring at install, so a release-10.0.0 writer is genuinely exercised against a 12.0.0-beta.6 reader; nothing fails on its merits.

test_venv_manager.py::test_lance_namespace_dependency covers the boundary directly, 9 passed with --run-compat. Checked non-vacuous by dropping the new tier, which fails exactly the two cases it should: assert 'lance-namespace>=0.8.0,<0.9' == 'lance-namespace>=0.11.1,<0.12'.

Not included

Everything else in upstream lance-format#8903, which is the dependency bump proper and is breaking: raising lance-namespace to 0.11.1 in Cargo.toml and all three lockfiles, java/pom.xml and four Java sources, python/pyproject.toml, python/lance/namespace.py and uv.lock. Upstream's summary of what that entails:

0.11 changes four LanceNamespace methods to return a response object instead of a bare value. Both bindings are updated to match, and callers need to unwrap.

That belongs in its own deliberate port and review rather than riding along with a CI unblock. Nothing here depends on it: the map describes what other releases require, so it is correct whether or not this fork has bumped its own pin.

[amunra]

Superseded by #67, which caps the discovered compat version matrix at the version under test instead of adding a namespace-pin tier.

This PR backported upstream's fix (lance-format/lance@1391e6cb7, lance-format#8903) and did unblock the install — 30 failed became 278 passed. But it leaves a release branch testing against its own future: release-10.0.0 was resolving 11.0.0 and 12.0.0b6 into its matrix, because both discovery queries are global rather than relative to the build. It also needs a new tier on every upstream namespace bump, so the same class of break returns.

With the matrix capped, no tier is needed — every remaining version predates the 0.9 era and the existing arm covers it.