Rename Samlier to SAMLscope and add production deployment

[sgrastar]

Summary

• rename the product, Java packages, configuration, UI, documentation, and development assets from Samlier to SAMLscope
• configure samlscope.com production deployment with Docker Compose, Caddy, SQLite persistence, and GitHub Actions
• preserve existing SQLite installations by continuing to use a legacy database file when present
• update G2 protected paths so renamed feasibility boundaries remain covered by signed approval

Validation

• ./gradlew check (passed before the G2 protected-path follow-up; the follow-up changes only Python validation metadata, documentation, and a JSON Schema identifier)
• .venv/bin/python tools/g1_docgen.py --check
• .venv/bin/python tools/g1_validate.py --structural-only (46/46)
• .venv/bin/python tools/g2_validate.py (20/21; expected pending renewed signed G2 approval)

Review note

The current G2 approval predates the product and package rename. Commit 3726e61fb01727a01d9660d50696e15066d81497 is the proposed renewed G2 target. A separate signed approval-only commit will bind the reviewed artifacts after independent review.