JSON node input

**Is your feature request related to a problem? Please describe.**

User has to enter nodes manually via GUI; this can be tedious.

Sometimes nodes are added in batches of 20 ore more by node operators.

It takes time for UI team to update the reference wallet.

The shipped list is static, the list of live nodes is dynamic.

**Describe the solution you'd like**

JSON input field in the reference UI with a brief description of required format.

```
[
{"node": wss://xyz.com, "description": "XYZ"},
{"node": wss://abcd.com, "description": "ABCD"},
{...},

]
```

**Describe alternatives you've considered**

The UI could allow for a config file input of nodes.

**Additional context**
I am currently aware of 200+ nodes of current or historic significance. I check them regularly, I know of 72 live today. The reference UI has had a dated list of 35 nodes since the last live worker, many of which are no longer live.

When companies like deex and walldex come online with large node offerings its should just be a cut, paste, and text format operation for the user to upgrade to new nodes.

**Screenshot**

New input for JSON formatted list would go here:


Start at the reference UI screen shown in the issue and trace how the static node list is loaded and edited. Check how node entries are currently represented, then determine where a JSON input and its required node and description fields would fit. Done means users can provide a batch of nodes in the documented format and the UI uses the resulting list.

Written by the indexing model from the issue text.