Migrate to `context.WithTimeoutCause`

[Wondertan]

Everywhere we use context.WithTimeout which always returns context deadline exceeded as an error, which is not informative. The context.WithTimeoutCause, on the other hand, allows users to pass the exact error cause. This way, one can always find which timeout was triggered.

[commie1]

Hi I would like to work on this issue, could you please assign it to me?

[Wondertan]

hey @commie1, you are now assigned, lmk if you need other context or have questions

[baldwin-sudo]

Hi i would like to work on this issue too , if the other guy didn't submit a pr yet .

[Wondertan]

They didnt, so feel free to try

[baldwin-sudo]

basically i should add custom error messages in the cause argument ,so debugging becomes easier ?
if not can you clarify more please !
(first time trying to contribute)

[Wondertan]

Generally this should help with debugging, improve devx/ux as there a better explanation of what is going and you can also catch the cause in future

[baldwin-sudo]

i submitted a pr , can you review