[WIP] FATES JSON parameter files

[rgknox]

Description of changes

These changes accommodate a JSON format to the FATES parameter file. This set of changes is synchronized with FATES 1493.

This is a work in progress.

Specific notes

1. CTSM/CIME is in charge of identifying the parameter file that is used by fates
2. CTSM finds an available unit number and passes that unit number and the parameter file name to FATES
3. The complicated coordination between CTSM/FATES that was necessary because FATES did not have access to the netcdf libraries is no longer required.
4. Parameter file reads in FATES previous occurred in two seperate instances (for pft variables and for everything else), which was weird, that is changed here.
5. This PR should contain updates to the testing code to handle a parameter file manipulation

Contributors other than yourself, if any:

CTSM Issues Fixed (include github issue #):

Are answers expected to change (and if so in what way)?

Any User Interface Changes (namelist or namelist defaults changes)?

Does this create a need to change or add documentation? Did you do so?

Testing performed, if any:
(List what testing you did to show your changes worked as expected)
(This can be manual testing or running of the different test suites)
(Documentation on system testing is here: https://github.com/ESCOMP/ctsm/wiki/System-Testing-Guide)
(aux_clm on derecho for intel/gnu and izumi for intel/gnu/nag/nvhpc is the standard for tags on master)

NOTE: Be sure to check your coding style against the standard
(https://github.com/ESCOMP/ctsm/wiki/CTSM-coding-guidelines) and review
the list of common problems to watch out for
(https://github.com/ESCOMP/CTSM/wiki/List-of-common-problems).