Do not append stacktrace to the message when throwing a std::runtime_error

[dalg24]

We used to include the call stack in the error message when throwing a runtime exception but it looks like we accidentally unconditionally disabled the functionality in the refactor #2226

EDIT decided to strip the stacktrace from the error message since it can be obtained on the user side when handling the error

[dalg24]

@ibaned please confirm that this was an oversight

[dalg24]

The last 3 commits are optional

[ibaned]

@dalg24 correct, I don't remember a specific reason why this was changed.

[dalg24]

The last 3 commits are optional

I decided to revert after discussing with Cezary since it was adding a dependency on GMock. We can revisit later.

[cz4rs]

Looks good to me.

[dalg24]

Retest this please

Solution proposed changed since the approval

[dalg24]

@ibaned @cz4rs I dismissed your reviews since I decided to propose a different resolution after discussing the changes on the developer Slack channel. #4672 appends the current call stack to the error message when calling Kokkos::abort() from the host. We feel like we shouldn't do the same when throwing an exception because the stacktrace can be added on the user side when handling the error and the error message may become unreasonably big.