feat: Enforce Backend CI Security Gates and DR Operations

[SharifIbrahimDev]

🛡️ Feature: Enforce Backend CI Security Gates and DR Operations

📋 Overview

This pull request implements comprehensive CI quality and security gates alongside critical Disaster Recovery (DR) and Deployment operations documentation, ensuring the backend maintains strict reliability and security standards.

Closes #373
Closes #375

🛠️ Changes Implemented

1. CI Security and Quality Gates (#373)

• Workflow Definition: Added .github/workflows/ci.yml that triggers on PRs and pushes to main.
• Quality Gates: Incorporates automated testing, linting via eslint, and enforces coverage thresholds.
• Security Scans: Integrates a multi-layered security pipeline:
  • Dependency Audit: Fails on High/Critical vulnerabilities (npm audit).
  • Static Analysis: Configured GitHub CodeQL for advanced vulnerability tracking.
  • Secret Scanning: Enabled TruffleHog to detect inadvertently committed credentials.
  • Container Scanning: Integrated Aqua Trivy to scan the generated Docker image for OS and library vulnerabilities.
• Artifact Drift Checks: Fails the build if generated artifacts are out of sync with the committed source.
• Sensitive Path Protection: Checks for modifications to /auth, /indexer, and /database, preventing auto-merge and flagging for strict human review.

2. Deployment & Disaster Recovery Docs (#375)

• Disaster Recovery (DISASTER_RECOVERY.md): Outlined strict Recovery Time/Point Objectives (RTO/RPO), shadow rebuild commands, indexer bootstrapping procedures, and chain reorg responses without relying on external non-authoritative state.
• Deployment Operations (DEPLOYMENT.md): Created copy-safe environment configuration templates, artifact checksum validation commands, and rollback procedures.
• Security Principle Enforcement: Both documents enforce the absolute authority boundary of the smart contracts and prohibit logging or hardcoding of production secrets.

🧪 Verification Plan

• CI Execution: Push this branch to a remote to trigger .github/workflows/ci.yml and ensure all steps pass.
• Documentation Review: Read through the markdown files to ensure the copy-safe commands align with the Ops team's expectations.

📝 Notes for Reviewers

• Ensure that the GitHub repository settings are configured to require these new status checks before merging.