Fix handling of exceptions raised inside TracePoint :call handling

[jeremyevans]

Previously, exceptions raised inside a TracePoint :call handler could
be handled by a rescue clause inside the method. However, TracePoint
:call handling should occur before the body of the method is executed.
Exceptions in TracePoint :call handling should be treated similarly to
exceptions raised when getting default values for arguments, and not
be rescued by exception handlers inside the method.

This fixes the issue by inserting a nop during rescue compilation, so
the start of the rescue catch table will definitely be after TracePoint
:call handling. It also works if you insert a nop during method
compilation, but I think it is better to make rescue handling slower
than than making method calling slower. Possibly this nop could be
optimized out in cases where it is not needed, but I was not able to
figure out how to do that. Hopefully someone with more knowledge of
the compiler will be able to do so.

Fixes [Bug #14479]

This apparently causes a failure in the typeprof tests, though I'm not sure
why that is.

[ioquatix]

Nice work, looks like a tricky issue!

[mame]

I don't know what is a correct behavior when an exception is raised in a TracePoint hook. I re-assigned this PR to @ko1.

The failure of TypeProf is not a big deal. I will be happy to change the test if this change is accepted.