Decrease request_timeout in builders to avoid panics

[elmattic]

Summary of changes

Changes introduced in this pull request:

• Decrease request_timeout value in WsClientBuilder and HttpClientBuilder to avoid panics (see logs below)

Rational:

We don't need to handle timeouts at the jsonrpsee client level since we shim our own timeouts during the call, but setting it to some max value seems unsafe.

Setting a 10s timeout and simulating a slow endpoint in forest daemon:

$ FOREST_RPC_DEFAULT_TIMEOUT=10 ./forest-tool api compare --lotus /ip4/127.0.0.1/tcp/1234/ws --forest /ip4/127.0.0.1/tcp/2345/ws forest_snapshot_calibnet_2024-04-19_height_1539740.forest.car.zst --filter EthChainId
Request dump: RpcRequest { method_name: "Filecoin.EthChainId", params: Null, result_type: PhantomData<serde_json::value::Value>, api_version: V1, timeout: 10s }
Request params JSON: null
Lotus response: "0x4cb2f"

| RPC Method          | Forest              | Lotus |
|---------------------|---------------------|-------|
| Filecoin.EthChainId | InternalServerError | Valid |
Error: Some tests failed

Reference issue to close (if applicable)

Closes

Other information and links

$ RUST_BACKTRACE=1 ./forest-tool api compare --lotus /ip4/127.0.0.1/tcp/1234/ws --forest /ip4/127.0.0.1/tcp/2345/ws forest_snapshot_calibnet_2024-04-19_height_1539740.forest.car.zst --filter EthChainId
thread 'tokio-runtime-worker' panicked at library/std/src/time.rs:417:33:
overflow when adding duration to instant

Change checklist

• I have performed a self-review of my own code,
• I have made corresponding changes to the documentation,
• I have added tests that prove my fix is effective or that my feature works (if possible),
• I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

[ruseinov]

looks good.

nit: I'm still unsure what does // we handle timeouts ourselves comment mean, but it's perhaps out of scope anyway.

[elmattic]

looks good.

nit: I'm still unsure what does // we handle timeouts ourselves comment mean, but it's perhaps out of scope anyway.

Check this code: https://github.com/ChainSafe/forest/blob/main/src/rpc/client.rs#L65-L97

[hanabi1224]

overflow when adding duration to instant

This seems like a bug in upstream lib, should we PR a fix as well?