cosmos-xenna: Add version 0.5.11 - #4771

cosmos_xenna/file_distribution/_file_distribution.py does a top-level
import tqdm, but tqdm isn't declared anywhere in pyproject.toml
(dependencies or any optional-dependencies group). Upstream's own
uv.lock only carries tqdm in transitively, through huggingface-hub
and transformers in the examples extra, which uv.lock pulls in by
default. A plain pip install of the wheel never gets tqdm, so
collection blows up as soon as pytest imports file_distribution
(via pipelines.v1 and pipelines.private.pipelines), aborting all
21 test files that import it.

This is an upstream packaging gap, but there's nothing to patch in
our own install_requires here, so list tqdm explicitly for the
test step. It's a pure Python (py3-none-any) wheel, so it installs
fine from either index with no riscv64 build involved.

_publish-wheel.yml now requires a matrix input (main's "publish:
Validate effective wheel targets"), but this PR branch forked before
that landed and cosmos-xenna has never been merged to main, so
build-cosmos-xenna.yml never picked up the matching one-line update
every already-published package's workflow got. The merge ref
combines the new required-input _publish-wheel.yml with this branch's
old build-cosmos-xenna.yml, so every run has failed startup with
"Input matrix is required, but not provided".

Pass it the same way the mass-update commit did for every other
package's publish job.

5 non-slow tests (test_batch_size_hang, test_batching, test_empty_return,
test_serving, test_setup_on_node) failed with 'Not enough CPU resources
to run pipeline' or a stalled queue read. cosmos_xenna's own tests scale
their Ray resource requirements down via is_running_in_cicd(), which
upstream's ci.yml enables by setting IS_RUNNING_IN_CICD=1 - but
cibuildwheel's podman container doesn't forward that from the runner,
so the tests used their full-size (non-CI) requirements against a
3-CPU cluster and asked for more than was available. Setting the same
env var in CIBW_TEST_ENVIRONMENT restores upstream's own CI sizing.