build(deps)!: bump lance-namespace to 0.11.1 across Java and Python

[wjones127]

The Java and Python lance-namespace pins had drifted several releases behind the Rust one: java/pom.xml was on 0.7.7 and python/pyproject.toml on >=0.8.5,<0.9, while Rust was already on 0.11.0. This bumps all three to 0.11.1, so the bindings stop being four releases apart from the core.

No feature work — this isolates the dependency drift ahead of ENT-2084 (multiple columns for the merge-insert on key), which needs a namespace release newer than any of these pins.

The Java changes are taken from #8623 and rebased onto current main. That PR's rest.rs tests are left out, as they cover vector index params (ENT-1892) rather than the version bump.

Breaking changes

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:

method	before	after	unwrap with
countTableRows / count_table_rows	Long / int	CountTableRowsResponse	.getCount() / .count
queryTable / query_table	byte[] / bytes	QueryTableResponse	.getData() / .data
namespaceExists / namespace_exists	void / None	NamespaceExistsResponse	—
tableExists / table_exists	void / None	TableExistsResponse	—

The implementations wrap the values the native layer already returns, so behavior is unchanged. Anyone implementing LanceNamespace themselves will need the same signature updates.

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.

Testing

Ran the namespace integration suite against LocalStack (--run-integration, 30 passed), which is otherwise skipped by default.

Not included

jackson-databind stays explicitly pinned at 2.15.2 in java/pom.xml while jackson-core, jackson-annotations and jackson-datatype-jsr310 now arrive transitively from lance-namespace-core at 2.18.3. That skew predates this PR but widens with it, and registering a 2.18 module on a 2.15 databind is the kind of mismatch that surfaces at runtime rather than compile time. Worth aligning separately.

Separately, [tool.pyright].include in python/pyproject.toml is an explicit allowlist that does not cover python/lance/namespace.py, so nothing type-checks these Python signatures against the ABC — unlike Java, where the interface makes a mismatch a compile error. The file carries a TODO: expand this list; adding namespace.py to it is a reasonable follow-up.