Add SunLit Security Libraries to Secure Frameworks

[kerberosmansour]

Summary

Adds SunLit Security Libraries to the Secure Frameworks section.

It's a Rust Cargo workspace of 12 published crates, OWASP Proactive Controls and MASVS-aligned, threat-model-first, dual-licensed MIT/Apache-2.0:

• secure_boundary — input validation, axum extractors, size/depth limits, HTML sanitization, CORS, Fetch Metadata
• secure_output — context-aware output encoding (HTML, JSON, URL, JS, CSS, XML, LDAP, shell)
• secure_identity — JWT/OIDC, JWKS, TOTP MFA, sessions, biometric/step-up auth
• secure_authz — deny-by-default RBAC + ABAC + temporal authorization
• secure_data — typed secrets, envelope encryption, Vault/AWS KMS/Azure KV providers, Argon2id, FIPS-readiness
• secure_network — TLS policy, SPKI cert pinning, cleartext detection
• security_events, secure_errors, secure_privacy, secure_resilience, secure_device_trust, security_core

Each crate has fuzz targets, property tests, and dev guides; the workspace ships a reference axum service plus a 54-route DAST smoke service.

I picked Secure Frameworks rather than splitting across Authorization & Authentication / Cryptography to avoid multi-section listicle inflation — happy to break it out if you'd prefer.