mlflow 3.2.0 already requires `pyarrow<22,>=4.0.0`, so the `mlflow<3.3`
bound implies the pyarrow cap wherever mlflow takes part in the
resolution. The explicit `pyarrow>=16.1.0,<22` added nothing, and it
broke test_flink_extra_constrains_shared_pyarrow_dependency, which
compares the core pyarrow spec by exact string.

Dropping it leaves all three CI requirement files byte-identical -- the
resolution is unchanged, including py3.12 coming down to pyarrow 21.0.0,
which mlflow drives rather than the removed bound.

pixi.lock shrinks to a metadata-only update: the recorded requires_dist
for the editable feast package now lists the four remaining bounds, and
no package version moves. It keeps pyarrow 24.0.0 in the pixi
environments, as master does.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Signed-off-by: Chaitany Patel <patelchaitany93@gmail.com>