docs(architecture): correct package lists and feature-to-feature boundary

Align the architecture docs with the current repo:

- Boundary matrix: feature may depend on core, feature, tooling — a
  feature may import another feature's public exports. overview.md,
  dependency-flow.md, and vertical-feature-spec.md all said the stale
  `feature -> core, tooling`.
- Optional-core lists completed with core-analytics, core-consent,
  core-dsr; tooling list completed with core-testing.
- Package count corrected to the accurate 19-package breakdown.
- BindContext table gained analytics, consentFactory, rateLimit.

Deeper drift (the HTML explainers, vertical-feature-spec §5/§9.5/§11)
is tracked in the local .tmp/ working note, not yet addressed.

docs/architecture/template-tiers.md

@@ -23,6 +23,8 @@ Plus all 5 feature packages: auth, blog, marketing-pages, navigation, media.
 | core-ui        | `pnpm turbo gen core-package ui`        | (none)  | (none)                              |
 | core-audit     | `pnpm turbo gen core-package audit`     | ADR-018 | docs/guides/audit-and-compliance.md |
 | core-analytics | `pnpm turbo gen core-package analytics` | ADR-024 | docs/guides/analytics.md            |
+| core-consent   | `pnpm turbo gen core-package consent`   | ADR-025 | docs/guides/consent.md              |
+| core-dsr       | `pnpm turbo gen core-package dsr`       | ADR-025 | docs/guides/dsr.md                  |
 
 ## Why optional