🔒 [security fix] Unsafe set_len without size validation in api.rs

[404Setup]

🎯 What: Added assert! statements to validate that the returned size from compression and decompression operations does not exceed the allocated capacity or buffer length before calling set_len or returning the size.
⚠️ Risk: Calling set_len with a size greater than the vector's capacity is undefined behavior in Rust, which could lead to memory corruption or out-of-bounds access.
🛡️ Solution: Implemented explicit bounds checks using assert!(size <= bound) and assert!(size <= output.len()) in compress_helper, decompress_helper, compress_into_helper, and decompress_into_helper within src/api.rs.

---

PR created automatically by Jules for task 1440824756357674605 started by @404Setup

[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.