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.

先閱讀 SentryTaskDecorator、SentryWrapper.wrapCallable 和 SentryWrapper.wrapSupplier，以了解它們目前的 hub 複製行為。此 issue 仍需決定預設的例外捕捉行為，以及 SentryTaskDecorator 是否需要個別處理；完成的標準是這些設計選擇已確定，且 wrapping API 一致地實作約定的行為。

由索引模型根據 Issue 內容生成。