fix exception raising

[kandluis]

What does this PR do?

Attach additional information and re-raise exception appropriately.

Using type(e)(<new message>) doesn't work for exceptions that have different number of parameters in the __init__. The existing code hides the original stack-trace which complicates debugging.
This change uses Python's built-in exception mechanism. See https://docs.python.org/3/library/exceptions.html#built-in-exceptions.

One possible drawback is that a new ValueError exception is raised (rather than the original).

Note:
We should probably try to discourage try/catch blocks that catch all exceptions (like this one) especially in library code.

Before submitting

• Was this discussed/approved via a GitHub issue? (not for typos and docs)
• Did you read the contributor guideline, Pull Request section?
• Did you make sure your PR does only one thing, instead of bundling different changes together?
• Did you make sure to update the documentation with your changes? (if necessary)
• Did you write any new necessary tests? (not for typos and docs)
• Did you verify new and existing tests pass locally with your changes?
• Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review

Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

• Is this pull request ready for review? (if not, please submit in draft mode)
• Check that all items from Before submitting are resolved
• Make sure the title is self-explanatory and the description concisely explains the PR
• Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?

Make sure you had fun coding 🙃

[awaelchli]

nice