Collect lower court details for new appellate filings

[nonprofittechy]

New appellate filings currently omit the originating court and case details, causing Tyler to reject fee quotes with LowerCourtText is required or does not match regular expression. This change collects those details before fees and keeps them visible and editable on the final pre-submission review screen.

Closes #266.

Changes

• Detect new appeals using the selected category's AppellateCase metadata, with a court/category-name fallback during catalog outages. Existing cases skip the lower-court questions.
• Require a listed lower court, originating case number, and caption; collect an optional judge name. Validate selections on the server and retain answers when validation fails.
• Load Illinois options from the EFSP court catalog, excluding appellate/supreme and test locations. Include 126 distinct Massachusetts lower-court code pairs from MACourts, retaining upstream provenance and grouping shared sessions into readable choices. The large JSON addition is the court mapping and its source metadata.
• Send lower_court_case and both test/production trial_court code fields in the shared fee/submission payload. Remove empty previous-case IDs and omit stale lower-court data for existing or non-appellate cases.
• Show the selected court's readable name and originating case details on Review with an Edit link. Require missing details before fees/review, and invalidate saved fee quotes when those details change.

Review and testing evidence

Evidence gist: four screenshots, browser assertions/options, and sanitized live fee result.

Check	Result
Massachusetts new appeal	Luna browser run passed from People through required lower-court questions to Review and Edit. Live-confirmed category 5796 / AppellateCase; selected Attleboro District Court (1764) from 126 mapped choices.
Illinois new appeal	Luna browser run passed through the same flow. Selected cook:law1; representative live-catalog codes were checked, while the browser stub supplies a small deterministic list and excludes appellate/test entries.
Existing cases	Separate browser checks in both states skipped the lower-court questions; Python tests also verify stale metadata is omitted for existing and non-appellate cases.
Fresh screenshot runs	Both states again routed from People into the questions, rejected an empty lower-court selection, showed saved details on Review, and preserved them through Edit.
Live Illinois stage quote	Authenticated TAC1 fee request returned HTTP 200, Tyler 0: No Error, and $0.00 with cook:law1, lower-court case details, an active test payment account, and a reachable test PDF.
Python	Full suite: 1,300 passed, 1 skipped. Final focused appeal/document-preview checks after mapping consolidation: 24 passed.
JavaScript	65 unit tests passed.
Static checks	Ruff, ty, ESLint, template formatting, Bandit, migration check, and whitespace checks passed. Full JavaScript lint passed with the unrelated local .venv-root-owned-BROKEN directory excluded; commit hooks checked the changed files normally.

The browser screenshots use synthetic users and an isolated local database with a read-only EFSP stub. They start downstream of upload/preparation; payment is seeded, and the browser visits Review directly from the payment page. The visible fee/disclaimer warnings are expected because the stub rejects fee POSTs with HTTP 501 and does not implement disclaimers or submission. The successful live Illinois fee request is a separate check. No court filing was submitted; live Massachusetts fees and production submissions were not exercised.

Reproduction commands are in efile_app/tests/appeal-new-case.spec.js; the dedicated playwright.appeal.config.js avoids the normal browser suite's live-login setup.

Screenshots

State	Required lower-court details	Final review and Edit
Illinois	Open full screenshot	Open full screenshot
Massachusetts	Open full screenshot	Open full screenshot

Massachusetts: required questions and final review