PM-5758: finish design submission limit handling

[jmgasper]

What was broken

The earlier PM-5758 fixes restored submission-limit configuration, guarded member uploads, enforced the limit atomically, and created Screening and Review scorecards for the latest configured number of Design submissions. QA still saw only the newest submission per member in Review, and Work Manager could stop displaying a saved limit immediately after saving a draft.

QA also repeated the checkpoint-versus-final submission failure in community-app. Investigation confirmed the merged follow-up already handles those submission types independently, but a later deployment from the older payload-cms branch overwrote the corrected dev bundle.

Root cause

The Review UI treated every finite limit as a boolean latest-only policy and relied on the API's isLatest flag, which identifies exactly one submission. It also grouped history without the configured count or exact submission type. Work Manager reset its form from a save response that can omit the submissionLimit metadata entry.

What was changed

• Resolve Design limits with the same metadata policy as review-api and Autopilot: finite Design challenges use latest X, missing or explicit-unlimited Design metadata shows all, and non-Design challenges remain latest-one.
• Rank complete history per member and normalized exact submission type before applying Screening or Review eligibility, without promoting older attempts or reintroducing ineligible rows.
• Pass all phase-eligible rows into reviewer and submitter Review tables instead of pre-filtering to isLatest.
• Preserve the submitted submissionLimit in Work Manager when a successful draft response omits that specific entry, while respecting a value returned by the API.

Deployment follow-up: redeploy current community-app develop and update/rebase payload-cms before it deploys again so the already-merged type-scoped guards from PR #7262 remain live.

Any added/updated tests

Added and updated coverage for finite counts of one and multiple submissions, unlimited and malformed metadata, backend-policy edge cases, independent contest/checkpoint histories, rank-before-eligibility, Screening selection, Review row forwarding, and Work Manager draft-save metadata preservation.

Validation:

• Ticket-focused tests: 8 suites, 126 tests passed.
• Lint passed.
• Production build passed with existing repository warnings.
• The full suite has 18 unrelated failing suites and 27 failing tests; the same failures were reproduced on untouched origin/dev, and all PM-5758 tests pass.