🔒 Fix SQL Injection vulnerability in sqlite queries

[Tcode-Motion]

🎯 What: The sqlite.execute and sqlite.query functions previously took un-parameterized SQL strings, directly executing them. This made any user-constructed SQL string (like string concatenation for dynamic queries) vulnerable to SQL injection.
⚠️ Risk: Left unfixed, malicious users or tainted inputs could inject arbitrary SQL commands (e.g., DROP TABLE, OR 1=1) leading to data loss, unauthorized access, or database corruption.
🛡️ Solution: The functions were updated to accept an optional third argument (a list of parameters). These parameters are mapped from RuntimeValue to rusqlite::types::Value and safely bound to the prepared statement using rusqlite::params_from_iter, mitigating the SQL injection vulnerability. Existing scripts that do not pass a third parameter are gracefully handled by defaulting to an empty parameter list.

---

PR created automatically by Jules for task 16742585625164495187 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.