Document table data requirements and parsing behavior

[wlhunt]

Documenting:
-acceptable conditions, such as NANs in a float column
-unacceptable conditions, such as duplicate column labels
-conditions for Slycat rejecting the table
-conditions when Slycat accepts a table and enacts particulars guards on the data
-any difference in behavior between browser wizard ingestion and alternate client behavior

[wlhunt]

Adding comments and additional requirements.

Relocate the primary ingestion data format section of the Slycat User Manual from within the Parameter Space Model section to its own sub-section under the Overview Section.

Create an Input Data Format section between Models and Bookmarks:

Re-phrase the PS section and the CCA sections to refer to the Overview/Input Data Format section for format details.

The CCA section should lightly discuss the requirements of the user-chosen input and output data columns, with respect to the math operations of CCA.

The Overview/Input Data Format section should mention the Dakota tabular and HDF5 files.

Perhaps this is also a place to mention file source options, like: local/server/remote/smb. Verify this is also documented elsewhere.