fix(release): enforce crate dependency order

[ZhiXiao-Lin]

Summary

• raise internal A3S Box crate requirements from 3.0 to the actual minimum 3.1 API used by this release
• wait for each newly published crate to appear in Cargo's sparse index, not only the crates.io HTTP API

Root cause

A publish dry-run for a3s-box-runtime selected a3s-box-core 3.0.10, which lacks APIs introduced in 3.1.0. The release already publishes in dependency order; these minimum requirements make Cargo enforce that order and prevent verification against an incompatible older crate.

Validation

• cargo metadata --locked --no-deps
• cargo fmt --all -- --check
• cargo publish --locked -p a3s-box-core --dry-run --allow-dirty
• dependent crate package contents were validated before tightening the minimum version
• cargo info a3s-runtime@0.2.0 --registry crates-io verifies sparse-index visibility
• release YAML parses and the changed Bash block passes bash -n