chore(deps): upgrade pyballista to DataFusion 54

[djanand]

Which issue does this PR close?

Closes #.

Rationale for this change

#1906 upgraded the main workspace to DataFusion 54, but the python/ sub-project (a separate Cargo workspace that path-depends on the ballista crates) was left pinned to DataFusion 53. As a result, python/ now mixes two DataFusion majors: pyballista compiles the ballista path-deps against datafusion 54 while its own datafusion dependency resolves to 53, which fails to build:

the trait bound datafusion::prelude::SessionConfig: ballista::extension::SessionConfigExt is not satisfied
  = note: there are multiple different versions of crate datafusion_execution in the dependency graph

This PR brings python/ up to DataFusion 54 so the python build is consistent again.

What changes are included in this PR?

Bump the python/ sub-project from DataFusion 53 to 54, keeping both ecosystems in lockstep:

• python/Cargo.toml — datafusion, datafusion-proto, datafusion-python → 54
• python/pyproject.toml — datafusion==54
• python/Cargo.lock — regenerated (now resolves a single datafusion major, 54)
• python/uv.lock — regenerated (datafusion python package → 54)

No source changes were required
Verified locally: cargo check, maturin develop, and pytest (73 passed, 1 skipped) all succeed against DataFusion 54.

Are there any user-facing changes?

The ballista Python package now builds against and requires DataFusion 54 (datafusion==54). No API changes to the package itself.

No breaking changes to public Rust APIs.

[coderfender]

LGTM ! Pending CI