Add possibility to include self-defined Jsonrpsee Client in Wrapper struct

[haerdib]

E.g. add new function to create a JsonrpseeClient wrapper but with a user defined client here:

substrate-api-client/src/rpc/jsonrpsee_client/mod.rs

Lines 35 to 50 in 3098812

	impl JsonrpseeClient {
	pub async fn with_default_url() -> Result<Self> {
	Self::new("ws://127.0.0.1:9944").await
	}
	pub async fn new(url: &str) -> Result<Self> {
	let uri: Uri = url.parse().map_err(|e| Error::Client(Box::new(e)))?;
	let (tx, rx) = WsTransportClientBuilder::default()
	.build(uri)
	.await
	.map_err(|e| Error::Client(Box::new(e)))?;
	let client = ClientBuilder::default()
	.max_notifs_per_subscription(4096)
	.build_with_tokio(tx, rx);
	Ok(Self { inner: Arc::new(client) })
	}

Example:

pub async fn with_client(client: Arc<Client>) -> Self {
	Self { inner: client }
}

I'd also propose to make the inner client public - then the user may change settings any time.

[masapr]

I don't think we should make the inner client public. We don't want anyone to change the client during the running program (what happens e. g. with subscriptions, when I exchange the client? What happens with running processes? We would have to handle all these cases.).

But adding a constructor which takes a custom JsonrpseeClient is fine. I don't see any problem with that.

[haerdib]

That is true, but this way no one can access the inner convenience functions, such as is_connected (see here: https://github.com/paritytech/jsonrpsee/blob/master/core/src/client/async_client/mod.rs#L458-L490). We could also forward them, but then we'd need to make sure that we stay up-to-date with these functions.