`The property '...' is set to ... which is out of range` is very unhelpful

https://github.com/actions/runner/blob/9426c35fdaf2b2e00c3ef751a15c04fa8e2a9582/src/Runner.Worker/IssueMatcher.cs#L529

Test case:
https://github.com/check-spelling-sandbox/upgraded-garbanzo-vigilant-journey/commit/91674afb28ffbd9bed25f160573878ccf554201e
Results:
https://github.com/check-spelling-sandbox/upgraded-garbanzo-vigilant-journey/actions/runs/22208910261

Annotations

2 errors
test
The property 'line' is set to 2 which is out of range
test
Unable to process command '::add-matcher::/home/runner/work/upgraded-garbanzo-vigilant-journey/upgraded-garbanzo-vigilant-journey/a.json' successfully.

Notes:

1. It'd be helpful if the error message reported a file name and line number (preferably as an annotation, this happens for unhappy workflows)
2. It'd be helpful if the problem matcher complained that the regexp field was not present
3. If you're going to complain about fields, it's best to complain in numerical sort order (1 before 2) instead of alphabetical key order (line before message)
4. I don't understand why failure to process a problem matcher is deemed as fatal. Problem matchers are merely aids to help people interpret logs, they aren't mission critical. What's critical is that a workflow run to completion.

Start in src/Runner.Worker/IssueMatcher.cs at the linked line and reproduce the behavior with the linked check-spelling commit and workflow run. Review the four requested improvements: more useful file and line diagnostics, reporting a missing regexp, numerical field ordering, and whether matcher failures should be fatal. Done means the resulting behavior addresses the agreed scope and the linked case no longer produces the unhelpful annotation.