chore: update pins to make CI clients integration to work again

[fresh-borzoni]

Client Integration has failed to start on every run since Sep 28. Apache's list of allowed actions dropped two versions the workflow pins: astral-sh/setup-uv v8.2.0 on Sep 27 and erlef/setup-beam v1.24.0 on Sep 28. GitHub rejects a workflow when any of its jobs uses an action outside that list, so no job ran, including the Rust, C++ and Gateway jobs that use neither action.

This change moves setup-uv to v10.2.0 and setup-beam to v1.24.1. It also moves sccache-action from v0.0.10 to v0.0.11, because v0.0.10 leaves the list on Oct 22 and would stop the workflow again. All three versions are on the list with no expiry date, and each commit hash matches its release tag.

The setup-uv steps pass no inputs, so the breaking changes in v9 and v10, which change cache defaults, don't apply. This pull request edits the workflow, so its own Client Integration run checks the change.

Three tool releases since the last green runs break checks on unchanged code, so this pull request also fixes them.

mypy 2.4.0, released Oct 1, makes stubtest expect __rand__ and __ror__ next to __and__ and __or__. The Predicate stub now declares them.

The runner image now ships Rust 1.99. Its clippy rejects #[pyclass(from_py_object)] on ChangeType, because PyO3 0.28 generates a .clone() on that Copy enum. PyO3 0.29.3 fixes this. Until then, ChangeType uses skip_from_py_object, since no binding takes it as an argument.

The runner image also moved from Maven 3.9 to 3.10, which turns duplicate POM declarations from warnings into errors. fluss-fs-oss declared maven-jar-plugin twice, and fluss-flink-common declared flink-connector-base twice. Each module now has one declaration, and its effective POM is unchanged.

[fresh-borzoni]

@leekeiabstraction @charlesdong1991 PTAL 🙏