detailed sentry logs

Related to #8 (closed)

Reduced log complexity by throwing only 1 exception per function with an associated tag. When the error is thrown a log(debug) can be read in the breadcrumbs.

Errors will eventually fall down on "start" method, so i've put a captureMessage to reduce duplicates. In case an error was not handled, it would still throw a message from "start", and we can then retrace it from the breadcrumbs and the sentry traces to know where it appeared.

---

The goal is to easily see errors by tags with as much log details. Instead of having too much captureExceptions drowning the information.

This way of logging should be also added to sge and grdf konnectors.