fix(api): tally system rework

[mogery]

Summary by cubic

Reworked the billing tally flow to decouple billing from tally updates using a Redis-backed queue and a periodic worker. This reduces DB load and adds clear visibility into pending tallies.

• New Features
  • After successful billing, teams are added to a Redis set billed_teams.
  • The index worker runs every 5 minutes, processes up to 100 team IDs from the set, and calls update_tally_5_team for each.
  • Added Prometheus gauge billed_teams_count to track the backlog of billed but not yet tallied teams.

^{Written for commit 6393468. Summary will update automatically on new commits.}

[cubic-dev-ai]

No issues found across 3 files

[mogery]

@cubic-dev-ai re-review pls

[cubic-dev-ai]

@cubic-dev-ai re-review pls

@mogery I've started the AI code review. It'll take a few minutes to complete.

[cubic-dev-ai]

1 issue found across 3 files

Prompt for AI agents (all 1 issues)

Understand the root cause of the following 1 issues and fix them.


<file name="apps/api/src/services/billing/batch_billing.ts">

<violation number="1" location="apps/api/src/services/billing/batch_billing.ts:322">
Redis enqueue for billed teams lacks error handling, so a Redis hiccup makes `supaBillTeam` reject after billing succeeds, dropping the queue item and leaving the team never tallied.</violation>
</file>

_{Reply to cubic to teach it or ask questions. Re-run a review with @cubic-dev-ai review this PR}