Explore restructuring status format since jobtype keys are on top-level of JSON

[Eo300]

Top level of status JSON should have more generic keys, rather than any of them being jobtype-dependent

Current:

# file: 'pdb2pqr-status.json'
{
    "jobid": "sampleId",
    "jobtype": "pdb2pqr",
    "pdb2pqr": {
        "status": "pending",
        "startTime": <some float number>,
        "endTime": <some float number>,
        "subtasks": [ ],
        "inputFiles": [ ],
        "outputFiles": [ ]
    }
}

The value for jobtype is also one of the top-level keys.

Options:

• Use a single status file, having a "jobs" top-level key containing an object with the individual job statuses
• Continue with the separate job files, and instead rename the third key (pdb2pqr in this case) to something like "details"

Requires change to Electrostatics/apbs-web to support new structure

[intendo]

The more I think about this, the more I think it is better to keep the files separate. If you combine the apbs and pdb2pqr status files, what would the jobtype become? This might lead to more problems than it solves.