v1.3.2 - Security Linter Hardening & Performance Hotfix

This release focuses on optimizing performance regressions introduced in recent cryptographic changes while hardening our security posture against false-positive static analysis alerts.

What's Changed:

⚡ Performance Hotfix (Vault Synthetic Seeding) The previous update replaced md5 with sha256 for deterministic hashing across the board. While this satisfied CodeQL for password storage, it introduced a significant bottleneck inside the Vault when generating the integer seed for Faker's synthetic data engine (random.Random(seed)).

Fix: Switched back to the highly performant md5, but explicitly passed usedforsecurity=False (supported in Python 3.9+). This guarantees 0ms latency impact without triggering FIPS compliance violations or linters.
🛡️ Security Linting & Suppressions Bandit and Ruff reported 4 distinct categories of security issues. These were false positives given the context of the proxy, and have now been properly suppressed with explicit inline justifications to prevent future LLM/linter regressions:

B104 / S104: Suppressed the warning for binding the proxy host to 0.0.0.0 (Explicitly required for Docker deployments).
S103: Suppressed the os.chmod warning. The sticky bit 0o1770 is intentionally applied to the socket directory for IPC security.
S311: Suppressed the warning for using random.uniform instead of secrets (Used for exponential backoff jitter, not cryptographic key generation).
S110: Suppressed warnings for try-except-pass blocks that silently drop failed metrics / logs to prevent catastrophic proxy failure.
🔄 Terminology Updates

Fully migrated all SYNTHETIC_CRYPTO and STATELESS_SYNTHETIC references to STATELESS_CRYPTO across the codebase, configuration schemas, and documentation to accurately reflect behavior.

Full Changelog: v1.3.1...v1.3.2