And additionally, get rid of cases where we catch ParseErrors. Theoretically, all parsers should just call setFailed if there was an issue, and parses should check pstate.status to see if a child parser failed, and act accordingly. Throwing and Catching parse errors shouldn't really be necessary. We think maybe this was needed for Saxon, but that is gone. Need to determine if anything else actually relies on this behavior.

Note that in addition to making things more consistent, getting rid of withParseErrorThrowing could maybe have a performance boost, since that actually allocates an anonymous function.