chore(release): bump SOF crates to 0.10.0

[Lythaeon]

Description

Bump the published sof, sof-tx, and sof-gossip-tuning crate versions to 0.10.0, and align the public API/docs with the submit_signed(...) / submit_unsigned(...) split.

This matters because main now carries additive sof-tx changes that warrant a new crate release, and the public docs and install snippets should advertise the new crate versions and the clearer unsigned submit naming at the same time.

Changes

• crates/sof-observer/Cargo.toml
  • bump sof crate version from 0.9.2 to 0.10.0
  • update the internal sof-gossip-tuning dependency to 0.10.0
• crates/sof-tx/Cargo.toml
  • bump sof-tx crate version from 0.9.2 to 0.10.0
  • update the internal optional sof dependency to 0.10.0
• crates/sof-gossip-tuning/Cargo.toml
  • bump sof-gossip-tuning crate version from 0.9.2 to 0.10.0
• Cargo.lock
  • update workspace package entries for sof, sof-tx, and sof-gossip-tuning to 0.10.0
• crates/sof-tx/src/submit/client.rs
  • rename submit_builder(...) to submit_unsigned(...)
  • rename submit_builder_with_context(...) to submit_unsigned_with_context(...)
• crates/sof-tx/src/submit/client_builder.rs
  • update comments to match the unsigned submit terminology
• crates/sof-tx/src/submit/types.rs
  • update error comments to match the unsigned submit terminology
• crates/sof-tx/src/submit/tests.rs
  • update tests to use the renamed unsigned submit API
• README.md
  • update public dependency snippets to 0.10.0 for sof and sof-tx
• crates/sof-observer/README.md
  • update sof install snippets to 0.10.0
• crates/sof-tx/README.md
  • update sof-tx install snippets to 0.10.0
  • switch code examples to submit_unsigned(...)
• docs/gitbook/getting-started/install-sof.md
  • update install snippets to 0.10.0
  • keep the starter examples aligned with the renamed submit API
• docs/gitbook/crates/sof.md
  • update sof dependency snippets to 0.10.0
• docs/gitbook/crates/sof-tx.md
  • update feature snippets to 0.10.0
  • switch examples to submit_unsigned(...)
  • add an explicit Jito code example instead of only mentioning it in prose
• docs/gitbook/operations/deployment-modes.md
  • update sof dependency snippets to 0.10.0

For slice-related changes:

• Affected slices
  • sof observer/runtime crate packaging
  • sof-tx transaction SDK packaging and public API naming
  • sof-gossip-tuning crate packaging
• Cross-slice communication changes (if any) and why
  • none
• Migration requirements (if any)
  • consumers using submit_builder(...) should switch to submit_unsigned(...)

Motivation

Business motivation:

• prepare the next published release of the three user-facing crates
• keep copied install snippets and docs consistent with the release users will actually consume

Technical motivation:

• the sof-tx API reads more cleanly as submit_signed(...) vs submit_unsigned(...)
• the docs should show the same naming the crate exposes
• the workspace-internal dependency versions should stay aligned for the release

Alternative approaches considered:

• release with the old submit_builder(...) name still exposed
• bump only sof and sof-tx while leaving sof-gossip-tuning behind

Scope and impact

• Affected slices: sof, sof-tx, sof-gossip-tuning, docs
• Data/API changes:
  • crate versions for sof, sof-tx, and sof-gossip-tuning move to 0.10.0
  • submit_builder(...) is renamed to submit_unsigned(...)
  • submit_builder_with_context(...) is renamed to submit_unsigned_with_context(...)
• Backward compatibility:
  • publishing-facing version bump is intentional
  • code using the old submit_builder(...) name must update
• Performance impact:
  • none beyond the already-merged sof-tx behavior changes on main
• Security impact:
  • none

Testing

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

Commands/results:

cargo make ci
cd docs/gitbook && npm run build

Related issues and documentation

• Fixes:
• Related:
• Architecture docs: docs/architecture/README.md
• Relevant ARD/ADR:
• 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