chore(forgejo): re-trigger apply of git.timeout/gc.auto (changed-stack skip)

910d5892 landed the [git.timeout] + [git.config] env in master, but the CI apply
skipped stacks/forgejo (the changed-stack-diff race after a sync-merge), so the
Forgejo deployment never picked it up. A trivial comment touch to force a clean
apply of the stack so the durable push-mirror fix actually takes effect.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

stacks/forgejo/main.tf

@@ -217,6 +217,8 @@ resource "kubernetes_deployment" "forgejo" {
           #   2) lower gc.auto so post-push autogc + the cron keep repos PACKED —
           #      the real fix ([git.config] gc.auto).
           # Dotted section/key names use the _0X2E_ env-to-ini escape.
+          # (Re-applied 2026-06-19: the original commit's CI apply skipped this
+          # stack via the changed-stack-diff race, so this touch re-triggers it.)
           env {
             name  = "FORGEJO__git_0X2E_timeout__DEFAULT"
             value = "3600"