On exception pudb now jumps into the exception instead of showing it

**Describe the bug**

When you set a breakpoint with `pudb.set_trace()` and pudb stops, you can press *n* to execute the next statement. In the past if you the statement raised and exception, pudb would tell you that an exception was raised and pressing *e* let you inspect the exception. Since the release `v2022.01.02` `pudb` does not show the exception but instead jumps onto the function where the exception was raised.

**To Reproduce**
Steps to reproduce the behavior:
1. create a function that has raises an exception
2. write a function that calls the failing function and set a break point before the call with `pudb.set_trace()`
3. Press *n* to execute the failing function

**Expected behavior**

pudb should tell you that the function raised an exception, by pressing *e* you should be able to inspect the the exception

**Additional context**

While some some might consider thus a nice feature, it also has the huge drawback, that it takes out of the context you were debugging and you might not be able to jump back, specially on `asyncio` tasks where you end up on the aio-loop rather than on your initial breakpoint.

I already asked this question [on the discussions board](https://github.com/inducer/pudb/discussions/560) and it was suggested that I do a `git-bisect`. I did that and 98ccafc49c1d3b31a74987eebb6cb11ba2c89998 was found as the commit that introduced the bug.

**Versions**

- `v2022.01.02` on Python 3.10.4