[Feature] Dependency conflict: pypaimon 1.3.1 pins pyarrow==16

### Search before asking

- [x] I searched in the [issues](https://github.com/apache/paimon/issues) and found nothing similar.

### Motivation

Hi maintainers,

`pypaimon==1.3.1` currently pins `pyarrow==16`, which causes dependency conflicts with newer packages in the Python data ecosystem.

For example, in my case:

- `py-data-juicer[all]==1.5.1` depends on `pypaimon>=1.3.1`
- `datasets>=4.7.0` requires `pyarrow>=21.0.0`

This makes the environment unsatisfiable when both are needed.

Would it be possible to relax the `pyarrow` pin, or validate/support newer `pyarrow` versions?

If the strict pin is required, could you clarify whether this is due to API/ABI compatibility constraints?

Thanks.

### Solution

_No response_

### Anything else?

_No response_

### Are you willing to submit a PR?

- [ ] I'm willing to submit a PR!

No files or tests are named. Start by locating the pypaimon 1.3.1 dependency metadata and reproducing the resolver conflict with py-data-juicer and datasets; determine whether newer pyarrow versions are compatible. Done means the supported pyarrow range is documented and dependency resolution is validated by an appropriate test or installation check.

Written by the indexing model from the issue text.