feat(ws): add methods taking in a tungstenite config

[fulminmaxi]

Motivation

Currently the websocket implementation does not allow to pass in a custom Tungestenite config. For example, its not possible to increase the default msg size over the Tungestenite default, which can lead to Message Too Long errors if fetching a lot of events with a lot of fields in them, one case where I've seen this failure in practice is when fetching around 8k events like this one:

    event TradeRequested(
        address indexed tokenIn,
        address tokenOut,
        uint256 amountIn,
        uint256 minAmountOut,
        address recipient,
        uint256 indexed tradeIndex,
        address indexed trader
    );

Solution

This PR adds 2 new methods to the WsClient and the WsManager:

• connect_with_config which is the same as connect, but allows taking in a Tungstenite config object
• connect_with_config_and_reconnects which is the same as connect_with_reconnects, but allows taking in a Tungstenite config object.

PR Checklist

• Added Tests
• Added Documentation
• Breaking changes

[mattsse]

this mimics tungsenite's API and is an additional function so no breaking changes.

lgtm, pending nit

[mattsse]

can we link to tungsenite's connect functions here in the docs?

[fulminmaxi]

done

[mattsse]

nit:
make last argument so arg 1+2 are identical to connect_with_config

[fulminmaxi]

good point, done in last commit, I've also changed the name so its connect_with_config_and_reconnects which will make it pop in IDE hints once you already decided you want to use a config

[prestwich]

The config is discarded, so will not apply to successive reconnects. Need to modify the struct to store the Option, and the need to modify the reconnect function to use it if available

[prestwich]

wasm compilation is broken. I believe you'll need to add a few cfg blocks to the new reconnect logic and related imports

[prestwich]

can we DRY these? this and reconnect() are largely duplicated code. take the part that needs to be conditionally compiled and move it into a smaller function instead of duplicating the entire function

[fulminmaxi]

should be better now