Save, Load Race Data in Human Readable JSON format

[nojronatron]

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

Whenever I look at the output from Save Race Data button, I struggle to read and understand the data. Usually this isn't a problem because the data is stored for backup and for moving to a computer with Winlink Express installed and not looked at. But for instances where data verification is necessary (for whatever reason), reading through the current formatting is tedious (at best), and definitely time consuming.

I think this can be improved.

Describe the solution you'd like

When saving race data, the formatting should include newlines, and proper spacing and indentation for readability. This includes the bib records themselves: They should be properly comma-separated rather than tabs, and if possible, displayed as collections.
When loading race data, it should be able to read-in this neatly formatted data so as not to break

Describe alternatives you've considered

• Not changing anything: The problem of difficulty reviewing data remains.
• Writing out data to a single line: Will line-wrap too easily causing added difficulty reading the data.
• Simple JSON: Be default, a JavaScript JSON parser does not make human-readable JSON, rather machine-readable usually for REST calls or efficient data processing.
• JSON with tab-delimited bib records: The bib records are still difficult to read.

Additional context

An ideal output would look something like:

{
  "thisVersion": "2.0.0",
  "EventTitle": "Bigfoot FF Test",
  "MessageNumber": "1",
  "address": "N0CALL",
  "Location": "WM_Wright Meadow (Rd.9327)",
  "msgsubject": "Bigfoot FF Test Wright Meadow (Rd.9327) Message #1",
  "numlines": "4",
  "TheData": [
    "106,DROP, 1510, 24, WM", 
    "106, IN, 1510, 24, WM", 
    "105, OUT, 1510, 24, WM", 
    "105, IN, 1510, 24, WM",
    ],
  "Comment": "Testing FF.",
  "previousRecord": {
    "runner": "106",
    "action": "DROP",
    "time": "15:10",
    "dayOfMonth": "24",
    "location": "WM",
    "messageNumber": "1"
  }
}