Match result page

[erinz2020]

Backend:

Frontend:
Add new react page /react/match-results?taskId=xxx for match results, replace /iaResults.jsp, most functions should remain the same.

PR fixes #1474
PR fixes #561
PR fixes #1301
PR fixes #1338

[erinz2020]

@claude You are reviewing a code change as a senior engineer in an existing production codebase.

Your goal is to find only the most important issues that should realistically be addressed before merge.

focus on frontend only

Review principles:

Prioritize correctness, reliability, data flow, async behavior, state consistency, and real maintainability risks.
Do not comment on personal preference, code style, naming, or optional refactors.
Do not propose architecture changes unless the current implementation is clearly dangerous or broken.
Respect existing project conventions and favor minimal changes.
Do not invent missing requirements.
Be conservative: if something is acceptable, do not flag it.
Pay special attention to:

null / undefined access
React effect dependency mistakes
stale closures
race conditions
duplicate or inconsistent state
controlled/uncontrolled form issues
loading / error / empty-state logic
accidental rerenders with real impact
incorrect assumptions around async requests, polling, or derived data
Output:

Start with one line only:

"No merge-blocking issues found"
or "Found X important issues"
Then provide up to 3 issues only.

For each issue, use:

Severity: blocker | high | medium
Location: file / function / component
Problem:
Impact:
Minimal fix:
Do not include praise.
Do not include optional improvements.
Do not include “consider”, “might”, or “could” comments unless there is a concrete risk.