Skript/Server Version

dev/feature

Bug Description

When using the new SecCatchErrors which utilizes RuntimeErrorCatcher, turns out the results can be hindered from RuntimeErrorManager due to the "frame limit".
So using this new ability in tests for the test environments, will sooner or later fail because some errors are being rejected in RuntimeErrorManager because the limit for that frame has been reached, thus causing no errors to be caught in RuntimeErrorCatcher and then not updating ExprCaughtError.

Expected Behavior

RuntimeErrorManager to bypass the frame limit when the error being printed is going to be caught by a RuntimeErrorCatcher.

Steps to Reproduce

Make atleast 8 tests using SecCatchErrors with the intent to have an error thrown and caught. Then assert the ExprCaughtErrors

Errors or Screenshots

No response

Other

No response

Agreement

• I have read the guidelines above and affirm I am following them with this report.

Can be seen in this PR

additional context