Make --interactive-debugging run pry in the failure's context
It feels limiting using --interactive-debugging
and being dropped in the debugging REPL without the failure's context, especially now that we have #20305 (closed) when manually adding a pause()
breakpoint. In fact, I believe this will make --interactive-debugging
kinda useless compared to seeing the error and instead restarting after adding the breakpoint just before the line the error occurred.