Rename workspace member `near-jsonrpc-client` to avoid name collision

[mooori]

There is an (unpublished) workspace member named near-jsonrpc-client:

nearcore/chain/jsonrpc/client/Cargo.toml

Lines 1 to 2 in a4d9451

	[package]
	name = "near-jsonrpc-client"

That name collides with a crate published on crates.io that lives in another repo.

This can cause confusion, in particular since /benchmarks/synth-bm depends on the near-jsonrpc-client from crates.io, while other workspace members depend on the unpublished crate with the same name.

To resolve this, the crate in /chain/jsonrpc/client should be renamed. Since it is not published, that shouldn't cause issues elsewhere.

[qiweiii]

Is nearcore-jsonrpc-client an acceptable name? if so I can help update.

I also found near-jsonrpc-primitives have the same problem, should I update it to nearcore-jsonrpc-primitives as well?

[mooori]

Is nearcore-jsonrpc-client an acceptable name?

Most (or maybe even all) crates in nearcore have names starting with near-. For consistency I would keep that prefix. Perhaps something like near-jsonrpc-client-internal. Or you could check what the crate does and try to come up with a more descriptive name. The new name just shouldn't conflict with any crate in nearcore or on crates.io. And yes, a PR to update the name would be welcome :)

near-jsonrpc-primitives

This one looks actually fine since it is published from nearcore. So there is no name conflict.

[qiweiii]

I didn't think of a better name than near-jsonrpc-client-internal, and just put up a PR