When wrapping callable / supplier / task we could automatically capture exceptions

### Problem Statement

Currently `SentryTaskDecorator`, `SentryWrapper.wrapCallable` and `SentryWrapper.wrapSupplier` only clone the hub to ensure scope does not leak but do not automatically capture errors.

### Solution Brainstorm

We could add overloads for the wrap methods to automatically capture.

TODO: decide on default behaviour

Maybe it makes sense to split out `SentryTaskDecorator` as it could get more complicated when developers want to decide which tasks to automatically capture errors for and which not.