bug: development branches are counted toward the preview branch limit on the Manage/Limits page #4281

Provide environment information

v4.5.0+

Describe the bug

On the org Manage/Limits page, the "Preview branches" usage count includes DEVELOPMENT branches, not just preview branches. The number is also shown against the preview-branch limit, so it can display nonsensical over-limit values (e.g. "12 / 5" when most of those are dev branches).

Expected: the "Preview branches" count should only reflect active preview branches. Dev branches and preview branches are separate features with separate limits and should not share a counter.

Reproduction repo

n/a

To reproduce

1. Have at least one active development branch, on a plan with a preview branch limit (Hobby/Pro).
2. Open the Manage/Limits page and note the "Preview branches" count.
3. Archive a development branch.
4. Observe the "Preview branches" count decreases by 1, even though no preview branch was archived.

Additional information

Display-only bug — actual quota enforcement is correct. checkBranchLimit (apps/webapp/app/services/upsertBranch.server.ts) enforces two separate limits: PREVIEW -> "branches", DEVELOPMENT -> "branchesDev". Dev branches do NOT actually consume the preview quota; only the displayed number is wrong.

Root cause: the count in apps/webapp/app/presenters/v3/LimitsPresenter.server.ts (~line 155) filters only on branchName != null / archivedAt: null with no type filter, so it counts DEVELOPMENT branches too, then renders that total against the preview ("branches") limit.

Fix: add type: "PREVIEW" to the count's where clause (and parentEnvironmentId: { not: null } to mirror checkBranchLimit and exclude the branchable parent).

Note: not related to branch origin — the count ignores branch type entirely, so it happens regardless of whether branches came from merged PRs, trigger dev, etc.