fix(parser): gracefully handle stalled parser in object patterns

[arendjr]

Summary

Fixes #4622.

In some cases, ) and ] could cause the parser to stall inside object patterns, triggering an internal assertion.

I was initially able to create a very specific fix by checking for these two characters, but it also created some fallout in other snapshots. Those snapshots were also for error cases, so it wasn't a dealbreaker, but the fix itself also felt brittle: what if another character or combination could trigger a stalled parser too?

So instead I changed how ParserProgress works, allowing us to gracefully handle stalled parsers. This way we don't fail with an assertion, but we can provide a nice diagnostic.

Test Plan

Test case added.

[codspeed-hq]

CodSpeed Performance Report

Merging #5198 will not alter performance

_{Comparing arendjr:fix-error-recovery-on-invalid-objects (c4b6113) with main (0750b40)}

Summary

✅ 97 untouched benchmarks