PM-6510 Mark timed-out Marathon Match tests as failed -> dev

[jmgasper]

Related JIRA Ticket:

https://topcoder.atlassian.net/browse/PM-6510

What's in this PR?

A timed-out Marathon Match submission could show Passed because the UI trusted the runner's completion status or treated any numeric score as a success. Resolve settled non-passing or negative results as Failed for both provisional and system testing, including legacy score fields, while preserving pending/cancelled lifecycle states, successful zero scores, and the newest retry result.

The attached timeout artifacts and the dev API both confirm the reported attempt failed: submission 4lwkAWaH6Vzg5f has repeated 10-second timeouts and -1 aggregates with isPassing: false in each scorer phase. The fix is confined to platform-ui; AWS access was unnecessary.

Validation:

• 177 tests passed across Marathon utilities, challenge detail flows, and submission history, including the provisional/system timeout regressions.
• yarn lint passed.
• NODE_OPTIONS=--max-old-space-size=8192 yarn run build passed on Node 22.13.0.