Common - Isolate PFH errors

[DarkBall123]

When merged this pull request will:

• Keep later PFHs and frame queues running when one PFH errors.

used the isNil suggestion from the issue so one broken PFH no longer stops the rest. ScriptError and the stack trace are still reported normally.

tested this with persistent and one-off errors, nested handlers, self-removal, adding and removing handlers during iteration, return values and delayed handlers. later handlers and frame queues kept running after an error, and the largest measured overhead was about 0.16 ms with 500 PFHs.

Fixes #1602

[DartRuffian]

Comment saying why it's there would probably be good

[PabstMirror]

What if we modify CBA_fnc_addPerFrameHandler to optionally wrap
that way there is no performance penalty for most users

params [["_function", {}, [{}]], ["_delay", 0, [0]], ["_args", []], ["_iWriteShitCode", false, [false]]];

if (_iWriteShitCode) then {
    _function = compile format ["isNil {%1}", toString _function];
};