fix(dev): validate integration version bumps

[Xuanwo]

Which issue does this PR close?

Follow-up to #8008.

Rationale for this change

object_store_opendal 0.58.1 upgraded object_store from 0.13 to 0.14 under a patch release, which broke downstream trait compatibility. The release tool currently trusts manually selected package versions and can repeat this mistake when an integration exposes types or traits from an incompatible dependency line.

What changes are included in this PR?

Before writing any files, update-version now compares configured public compatibility dependencies with the latest reachable final release tag. It requires object_store_opendal and parquet_opendal to cross the corresponding Cargo compatibility boundary when opendal, object_store, or parquet does.

The check uses the planned OpenDAL version from the release package graph and external dependency versions from the integration manifests. Missing release tags and unsupported dependency requirement shapes fail with actionable errors.

Are there any user-facing changes?

Release managers receive an error before version files are updated when an integration target is incompatible. Library APIs and runtime behavior do not change.

AI Usage Statement

Codex materially assisted with repository and release-history analysis, implementation, and regression-test design. The change assumes the latest reachable non-prerelease tag represents the release baseline and accepts dependency requirements with one caret, exact, or tilde comparator; other requirement shapes fail closed.