Use Rpc handles in NodeClient

[mattsse]

Describe the feature

after #15956 we currently rely on a patch of jsonrpsee

we can get rid of this if we replace what we store for:

reth/crates/e2e-test-utils/src/testsuite/mod.rs

Lines 26 to 29 in b15c1c8

	/// Regular JSON-RPC client
	pub rpc: HttpClient,
	/// Engine API client
	pub engine: HttpClient<AuthClientService<HttpBackend>>,

we can instead store the server handles

reth/crates/node/builder/src/rpc.rs

Lines 42 to 45 in b15c1c8

	/// The regular RPC server handle to all configured transports.
	pub rpc: RpcServerHandle,
	/// The handle to the auth server (engine API)
	pub auth: AuthServerHandle,

TODO

• instead of storing the HttpClient, store the serverhandles in NodeClient which is initialized here:
  

  reth/crates/e2e-test-utils/src/testsuite/setup.rs

  Line 166 in b15c1c8

  node_clients.push(crate::testsuite::NodeClient { rpc, engine });

• add some helper functions to obtain the engine client to replace direct use like

  reth/crates/e2e-test-utils/src/testsuite/actions.rs

  Line 352 in b15c1c8

  let engine_client = &client.engine;

Additional context

No response

[Ayushdubey86]

can i look into this?