RES-1892 Add ability to edit network data for groups.

[edwh]

We have a network_data field for groups. This is JSON-encoded. This PR exposes editing of that for network coordinators on the groups page.

A separate text input is created with a suitable label for each entry in the JSON object.

There's a button to allow you to add a new (empty) entry, which effectively allows you to extend the schema. You can't delete them, though, as that is a bit dangerous.

I've done this for groups only, though we may choose to extend it to events too.

[ngm]

Great stuff, all looks good to me.

@edwh Out of interest, why do we need the checks for whether the network_data field is a string or not?

[sonarqubecloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
2 Code Smells

No Coverage information
4.3% Duplication

[edwh]

@edwh Out of interest, why do we need the checks for whether the network_data field is a string or not?

I wondered if you'd ask. I think it was to do with how Laravel handles JSON fields on different database versions. That should be transparent to the user whether or not it is stored in the DB as a JSON or TEXT field. But I saw a case in testing when it wasn't, so I put that in and didn't think much further.