Error recovery

[PieterOlivier]

This is a feature-tracking PR, will remain draft while we are working on the error recovery feature. Other smaller PRs will target this branch, and when ready we can merge this one. Where possible we try to do most of the reviewing in the open PRs that target the error-recovery branch, but sometimes stuff is missed there, and then it's better to comment on changes in this global-tracking-PR.

History:

• in 2012 @jurgenvinju wrote an initial implementation of parser recovery that was based on user supplied recovery hints.
• in 2022 @jurgenvinju resurrected that recovery attempt and got into a decent shape, now without user supplied recovery hints, but lacked bandwidth to finish it.
• in 2024 @PieterOlivier picked this backup as part of swat.engineering's effort to invest in some larger scale rascal infrastructure improvements.
• Implement basic error recovery #2020 the first PR that was reviewed and merged into this feature branch.
• Test support for error recovery #2034 testing of error recovery in examples in multiple languages and intensive testing of Rascal sources files
• Reimplemented error tree disambiguation in Java #2035
• Error recovery #2033 an old tracking branch (we had to rename it to add CI support for branches targetting this PR)
• Moved error recovery functions from ParseTree to util::ErrorRecovery #2042
• Reimplemented findAllErrors function in Java #2043 implementation of findAllErrors in Java, needed for rascal-lsp
• Support for parsing input that forms a valid prefix #2053
• Trigger recovery when only recovery stacks are left #2057
• Fixed size inconsistency between allocating and enlarging #2062
• Added '\n' end matcher so end-of-line is also seen as skip terminator #2064
• Feat/remove auto disambiguation #2075
• Recovery/recover all productions #2108
• Safe memoization during parse graph flattening #2136
• Recovery/cleanup #2146

[DavyLandman]

What a great effort! Thanks everyone involved in making this work.

I'll be merging this PR now. It will be an experimental feature of the parse function, and in upcoming PRs we'll be working on integrating error trees with other rascal features. So if someone starts using it: be warned, this might change a bit along the way.