chore(release): prepare 0.9.2 — bump crate versions

[Lythaeon]

Description

Prepare the 0.9.2 release by bumping the published SOF crate versions, advancing the vendored gossip crate patch suffix, and aligning internal dependency and README version references. This keeps the workspace and release surface consistent after the merged gossip changes.

Changes

Detailed list of what changed:

• crates/sof-observer/Cargo.toml: bumped sof to 0.9.2, advanced internal dependencies to sof-gossip-tuning = 0.9.2 and sof-solana-gossip = 3.1.8-sof.4.
• crates/sof-tx/Cargo.toml: bumped sof-tx to 0.9.2 and updated the optional sof dependency to 0.9.2.
• crates/sof-gossip-tuning/Cargo.toml: bumped sof-gossip-tuning to 0.9.2.
• crates/sof-solana-gossip/Cargo.toml and crates/sof-solana-gossip/Cargo.toml.orig: bumped the vendored gossip crate to 3.1.8-sof.4.
• Cargo.lock, crates/sof-solana-gossip/Cargo.lock, and crates/sof-tx/fuzz/Cargo.lock: refreshed package entries to match the new crate versions.
• README.md, crates/sof-observer/README.md, and crates/sof-tx/README.md: updated published dependency snippets to 0.9.2.
• Any architecture/runtime/infra implications: none; this is a release/version alignment change only.

For slice-related changes, include:

• Affected slices: none functionally; workspace release metadata only
• Cross-slice communication changes (if any) and why: none
• Migration requirements (if any): none

Motivation

Business motivation:

• Prepare the next published release with consistent crate metadata and docs after the merged gossip work.

Technical motivation:

• Keep crate versions, internal path dependency versions, lockfiles, and README install snippets aligned so release packaging and consumer documentation match.

Alternative approaches considered:

• Bump only the publishable crate manifests and leave docs/lockfiles unchanged. Rejected because it leaves the workspace inconsistent and complicates release validation.

Scope and impact

• Affected slices: workspace manifests, vendored gossip crate metadata, release docs
• Data/API changes: none
• Backward compatibility: preserved
• Performance impact: none
• Security impact: none

Testing

• Unit tests
• Integration tests
• Manual verification
• Performance checks (if applicable)
• Security checks (if applicable)

Commands/results:

cargo make ci

Results:

• cargo make ci passed locally on chore/release-0.9.2.

Related issues and documentation

• Fixes:
• Related: release follow-up to the merged gossip worker/pinning changes on main
• Architecture docs: docs/architecture/README.md
• Relevant ARD/ADR: none required
• Operations/runbook updates: none

Reviewer checklist

• Code follows project standards and architecture constraints
• Slice boundaries are respected (docs/architecture/ard/0003-slice-dependency-contracts.md)
• Tests added/updated and passing
• Documentation updated (README/docs/operations as needed)
• No undocumented breaking change
• Performance trade-offs documented where relevant
• Security considerations addressed where relevant

Additional notes

• This PR only prepares the release metadata and docs; it does not introduce functional code changes beyond version alignment.