EPIC: Developer Experience, Cargo Xtask Profiles & CI/CD Pipeline Modernization

## Overview

This sub-EPIC focuses on eliminating developer friction, speeding up CI feedback loops, and providing matrix-level compile verification across all backend feature permutations.

## Goals

1. **Cargo Xtask Feature Matrix**: Adopt `cargo xtask` with support for a 9-profile matrix (`minimal`, `postgres`, `mysql`, `sqlite`, `aws`, `vault`, `gcp`, `azure`, `all`) and `check-profiles` matrix verification.
2. **Modular Local Development**: Introduce Docker Compose profiles (`db`, `observability`, `acme`, `aws`) so services can be spun up modularly.
3. **CI Decoupling**: Extract Helm and Kubernetes templating validation out of `CI.yml` into a dedicated `helm-checks.yml` workflow.
4. **Supply Chain Hardening**: Pin Dockerfile builder images by immutable `@sha256:...` digests.
5. **Local CI Mirroring**: Ensure `local-ci.sh` reliably mirrors remote GitHub Actions.

Start by checking `local-ci.sh` against `.github/workflows/CI.yml` to map the current local versus remote verification flow. Then inspect `Dockerfile`, `docker-compose` files, and any `cargo xtask` entry points to see where the 9 profiles can be introduced, and move Helm/Kubernetes validation into `helm-checks.yml`. Completion is done when profile-gated compose services exist, builder images are pinned by `@sha256`, and both local-ci and GitHub Actions run the same profile matrix checks.

由索引模型根據 Issue 內容生成。