Update RPC creates duplicate cosmos node instead of updating

[mhagel]

Describe the bug

In admin-panel, updating a Cosmos-based RPC by community_id creates an additional node, instead of updating the original.

Initial conditions

Environment:

Branch/Release version:

master
Browser:

Wallet:

Reproduction steps

Actual behavior

A new chain node is created

Expected behavior

The original node is updated

Screenshots / Video

Reporter

Additional context

cosmos_chain_id is the canonical ID for a chainNode. This can be leveraged to ensure duplicates are not made.

Related: #6070

[mhagel]

@jnaviask I just realized Node-Update isn't implemented yet. I should clarify. Do we want this? And if so, should it only be for Cosmos cases?

In the ETH case, if the node exists, we currently return an Error: "Node already exists" and do not update.