history diagnostics for FATES runs, including ilamb runs and spinup runs

When FATES is enabled, FATES can/will report a litany of history diagnostics, directly with the history IO routines. These are defined on the FATES side of the code, and are prefixed with "FATES_". ALL of these variables are only relevant on the naturally vegetated land-unit, and do not include zero's or any other values in the grid-level output from other land-units, they always use the no-data flag for those other landunits (therefore all spatial averages ignore everything outside of the nat-veg lu).

However, there are diagnostics that we want active during a FATES enabled simulation that are interpreted at the grid-level, and don't assume that the scale or domain of interest is only for naturally vegetated lands.

There are several things that need to be updated

1) various CLM-side diagnostics that are typically active during big-leaf (CN) runs should also be active during FATES runs, and therefore need to be enabled by passing over boundary conditions from FATES, these are things like carbon fluxes (GPP), and states (TOTVEGC). This is also necessary for ILAMB comparisons. @olyson has provided a list (too complicated to paste here), that shows all the history diagnostics used thus far for different confrontations

2) for AD simulations (and potentially other configurations) that are FATES enabled, we either need to temporarily remove un-activated diagnostics like GPP and NPP from namelist_defaults_ctsm.xml , or get those diagnostics activated when FATES is on. In the Jan 26 CTSM science meeting we identified that some of FATES variables with extra dimensions (such as PFT, mentioned @pollybuotte ) would also be useful to evaluate if spinups were complete, as forest succession is now a thing that can complicated or extend spinup times when FATES is turned on.