Add *_RTE, *_ANY_RTE and *_NO_RTE assertions

[Garados007]

These assertions check the current RTE state and create an error if its unexpected. This simplifies the user code to check for RTEs during runtime.

Close #339

[Garados007]

@t-b @MichaelHuth Ready for review.

[t-b]

Very nice addition!

The assertions work as expected. I do have some questions about the example though ;)

• TestWaveOp: Whitespace in separate commit would be nice. But why remove AbortOnRTE? And if that is the right thing to do the print message should not mention it anymore.
• TestWaveOpSafe: This seems to be a better way to do things. Can we maybe rename that test case? And I'm wondering why we still need to have the try/catch? With the new assertions I would just do

    INFO("checks if CustomUserFunction returns with no RTE")
    CustomUserFunction()
    CHECK_NO_RTE()

or?

[Garados007]

Whitespace in separate commit would be nice.

👍

But why remove AbortOnRTE?

I forgot to put it back after experimenting.

And I'm wondering why we still need to have the try/catch?

At this part I want to show that the user can now handle RTE and aborts differently. Previously, the user has to add AbortOnRTE and handle both in the catch-block.

[Garados007]

Fixed it.