Revert "Add caller stacktrace to rethrown RuntimeException (#17249)"

[mmedenjak]

This reverts commit 318b336. Reasoning is that it introduces
significant changes in the invocation handling and causes some tests to
start failing (see #6383).
An alternate or augmented solution must be considered.

EDIT: had to revert #17438 as well since it relied on a method in ExceptionUtil which was introduced by the above commit.

[puzpuzpuz]

I'm fine with correctness of the revert, but we need to reopen #17202 if we merge this one. And once we reopen it, we have a high prio defect with 4.0.3 milestone. So, we probably need to find a way to fix it.

[mmedenjak]

@puzpuzpuz I'm actually doubting the priority of that issue. It says:

This makes it hard to follow the stack trace. The solution is already available on the member side. This issue is to address the problems on the client-side.

To me it sounds like a usability enhancement, when debugging or analysing issues. And it's not a regression introduced in 4.0.3, seems like it's the consequence of a 4.0 PR (#15441).

[puzpuzpuz]

@mmedenjak OK, then the issue could be addressed in the next patch release.

[mmedenjak]

Thank you for the reviews, everyone! 🙇