[moetemp]

What was changed

This PR adds the streams cargo feature to the bridge, which links the Stream runtime crates and builds a runtime for the S6 backends. temporalio-streams has the runtime and the memory Store, and temporalio-streams-redis has the Redis Store.

• The feature is off by default and on in poe build-develop and every wheel build. fips turns it on too.
• StreamCallError is in every build, so Python can import it with the feature off.
• temporalio-streams comes from the Core submodule. [patch.crates-io] points the Redis crate's temporalio-common and temporalio-streams at the submodule, so the bridge sees one copy of each type.
• The TLS and fips features forward to the Redis crate, which links the Redis client.
• The linters skip the submodule, since it now has the crate's Python script of the shared vectors.
• Fork-only pins. The submodule is at K10 7bb4e727 on moetemp/sdk-rust, which has C1 and the shared crate until they merge. Cargo.toml takes temporalio-streams-redis by git from temporal-community/sdk-streams at R3 6e3ee499, and Cargo fetches it with the feature off too. Upstream pins the merged Core commit, takes the Redis crate from crates.io (KR) by version, keeps the patch and drops the git source.

Depends on G3 (#369), since K10 sits on C1, K1 to K10 (moetemp/sdk-rust#212 to #220) and R1 to R3 (temporal-community/sdk-streams#1 to #3). The base is G3's branch.
Part of the Brook review series.

Why?

The Stream runtime is Rust, so every SDK shares the Store logic and its rules. A Python build links it like the rest of Core.

Open question. With the feature off by default, a source build from the sdist has no Stream runtime, but the wheels have it. Should it be on by default once the crate is on crates.io?

Checklist

1. How was this tested:
   • poe lint, poe gen-docs, cargo clippy and cargo fmt on both feature sets, pytest tests/bridge, and cargo tree for one temporalio-common and no ring in the FIPS build.
   • Fork CI passes, except the arm jobs, since the fork has no arm runners.