🔒 [security fix] Add input length validation to query.py

[Kshitij-KS]

🎯 What: This PR addresses a security vulnerability where query_text was accepted without any length validation.

⚠️ Risk: Without validation, an excessively large input string could be passed to the embedding model and the vector database, potentially causing high CPU/Memory usage or application crashes (Denial of Service). It could also exceed the token limits of the LLM.

🛡️ Solution: Added a validation step after parsing arguments in query.py that checks if query_text exceeds 1000 characters. If it does, the program exits with a descriptive error message using parser.error().

---

PR created automatically by Jules for task 14188642868390699861 started by @Kshitij-KS

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