Update Software XSD to increase clarity of input/output data formats

[JohnLevander]

In the current XSD, we have "dataInputFormats" as a list. This gets confusing when we use this list to mean both "all the different types of formats this software will except" and "all the inputs required by this software."

We need to make dataInputFormats a list of something like a new "SoftwareInput" type. The Software Input type will describe 1. the input number (1,2,3, etc) and then formats allowed for that number.

An entry that defines a software input that requires a synthetic ecosystem might look like this...

<dataInputFormats>
<SoftwareInput>
<id>
1
</id>
<description>
Synthetic Ecosystem File
</description>
<dataFormats>
MIDAS-ISG:synthia-us-v2010
</dataFormats>
<dataFormats>
MIDAS-ISG:spew-us-format-v1.2.0
</dataFormats>
</dataInputFormats>

[jeffstazer]

• Transferred info from dataInputFormats/dataOutputFormats to inputs/outputs in the database (json)
• Updated the modal from the main page to show the dataFormats from the new location (inputs/outputs)
• Updated the edit page to allow insertion/editing of inputs/outputs.