🛡️ Sentinel: Fix configuration injection and enhance security linting

[google-labs-jules]

This PR addresses a configuration injection vulnerability in the project initialization script and enhances the project's security posture by enabling automated security linting.

🛡️ Sentinel: [HIGH] Fix Configuration Injection in rename script

🚨 Severity: HIGH
💡 Vulnerability: The scripts/rename.py script was susceptible to configuration injection. User-provided strings (like description or author) were used in re.sub replacements without sanitization, allowing for:

1. Newline Injection: Injecting arbitrary keys into pyproject.toml or mkdocs.yml.
2. Regex Backreference Injection: Using \1, \2, etc., in inputs to leak or manipulate parts of the file being edited.

🎯 Impact: An attacker or an accidental bad input could corrupt the project configuration, potentially leading to misconfigured builds or unexpected behavior when the template is initialized.

🔧 Fix:

• Added validation to reject newlines in all inputs and double quotes in most inputs.
• Properly escaped double quotes in the description field.
• Switched to using a lambda for re.sub replacements to ensure they are treated as literal strings.

🔒 Security Enhancement: Automated Security Linting

• Enabled the S (flake8-bandit) rule set in ruff to catch common security pitfalls in Python code (e.g., use of assert, insecure random number generation, etc.) during development and CI.

✅ Verification:

• Verified that scripts/rename.py correctly rejects inputs with newlines or quotes.
• Verified that the project passes the newly enabled security linting rules.
• Confirmed that existing tests still pass.

---

PR created automatically by Jules for task 1316022709772912683 started by @amrabed

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