[investigation] extend the reach of the error boundary protection

[caridy]

error boundary protection is only covering public methods, setters, and the main engine, it doesn't cover next tick invocations, and other goodies that we might be able to add. This issue is a placeholder for such investigation.

Follow up from #936

[ravijayaramappa]

GUS work item: W-6157832

[apapko]

@ravijayaramappa @caridy is this still relevant? I recall there were few iterations around error boundary.

[caridy]

well, I think that at least we should spike (RFC) on this to explain why any other protection is virtually impossible.