feat(net): accept persistent consumer cookie stores

[pathscale]

Chuzz needs one persistent cookie jar to participate in the provider's complete HTTP exchange. Previously an embedder could only ask Blitz to create its internal ephemeral jar, so a separate persistent wrapper missed cookies set on intermediate redirects and final error responses.

This re-exports reqwest's cookie-provider contract from blitz-net and adds a constructor that installs an embedder-owned jar on the provider's existing client. The fixture proves the same jar supplies the first request, receives the redirect cookie before the redirected request, and receives the final error response cookie. ps-blitz-net moves independently to 0.4.10; the rest of the workspace remains at its existing version. The ps-boa engine, runtime and GC dependencies use the compatible ^1.0 range; a fresh no-lock resolution selects one published 1.0.6 family. The publish workflow now asks Cargo metadata for versions instead of parsing Cargo.toml text.

Validation:

• cargo fmt --all -- --check
• cargo test -p ps-blitz-net --all-features (13 passed)
• cargo clippy -p ps-blitz-net --all-targets --all-features -- -D warnings
• cargo check -p ps-blitz-net --no-default-features
• cargo check -p ps-blitz-net --no-default-features --features cookies
• cargo package -p ps-blitz-net --allow-dirty
• publish-plan registry audit through Cargo metadata: every unchanged workspace crate resolves to its already-published version and skips; only ps-blitz-net 0.4.10 is unpublished and selected
• Chuzz cookie persistence tests against this exact networking source, WorkTable 1.9.0-beta1 source, and ps-boa 1.0.6 source (10 passed)