Request for comments: Unify exception throwing

[vaind]

We're currently throwing ObjectBoxException as well as Exception.

• Either get rid of the former or use it in all places?
• Or actually use more specific classes, depending on what kind of exception it is? Like ArgumentError, StateError and reserve the generic Exception for cases when we can't do any better?
• What's the best practice?

[greenrobot]

I think it would make sense to ...

• use general ArgumentError and the likes where they fit
• use DbException when something goes wrong with the db (after checking it's not e.g. a argument error internally).
• I cannot think of cases where a plain Exception would make sense; would have to be reviewed on an individual basis.