Proposition to refactor timeouts

### Is your feature request related to a problem?

Currently there is a lot of timeout everywhere, for Tasks, P2P request, Mining timeouts ...

This become complex to manage since some low level module such as HTTP in smart contract library would need mining timeout to adapt the request timeout.

### Describe the solution you'd like

We could have a new utility module to manage timeout, we could use this new module also for Task timeouts.

This could also reduce unexpected timeout error

### Additional context

_No response_

### Epic

_No response_

The issue names Task timeouts, P2P requests, mining timeouts, and HTTP in the smart-contract library, but no files, entry points, or tests. Start by mapping where these timeout values are defined and consumed across those areas. Done should mean the timeout behavior has a clear shared design and avoids the currently described cross-module mismatch.

Written by the indexing model from the issue text.