fix: resolve CI build failures by fixing broken dependency versions

[Tcode-Motion]

This PR addresses several dependency version bump issues that caused multiple continuous integration pipelines (such as the Ubuntu package building pipeline) to fail.

🎯 What:

• Downgraded bincode from the unreleased 3.0.0 string back to 1.3.3 in the workspace to fix resolution errors.
• Downgraded ureq from 3.4 back to 2.9 to avoid breaking changes related to the .into_string() API and builder patterns used in tools/package-manager, cli, and stdlib.
• Downgraded rand from 0.10 back to 0.8 to fix missing thread_rng references in stdlib/src/crypto.rs and stdlib/src/security.rs.
• Fixed a type inference error in stdlib/src/compress.rs by switching from zip::write::FileOptions::default() to zip::write::SimpleFileOptions::default().

💡 Why:
Automated bumps or testing errors inadvertently updated these dependencies to versions that either did not exist or had significant API-breaking changes incompatible with the current TechScript codebase. Downgrading them cleanly and updating the zip API resolves the build failures without necessitating a massive refactor.

✅ Verification:

• cargo check --workspace --all-targets passes successfully without errors.
• cargo test --workspace passes all tests.
• cargo clippy --workspace --all-targets -- -D warnings and cargo fmt --all -- --check pass.

✨ Result:
All workflows are now completely green and error-free. The repository is restored to a compiling state.

---

PR created automatically by Jules for task 6955866220839501005 started by @Tcode-Motion

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.