ctsm5.3.042: Update FatesColdAllVars history output

[glemieux]

Description of changes

This PR updates the fincl1 list of nominally inactive FATES history output with recent additions to the FatesColdAllVars history output. Resolves #3052.

Specific notes

This should be integrated after NGEET/fates#1338 has been merged into FATES main and the ctsm tag has been updated to a fates tag that is associated with said PR (or newer).

This should be coordinated with NGEET/fates#1252 as that PR makes changes to the output names that would otherwise break the test.

#3063 has been merged into this PR as well as that PR is B4B and we would like to integrate it prior to NGEET/fates#1350.

Contributors other than yourself, if any:

CTSM Issues Fixed (include github issue #): #3052

Are answers expected to change (and if so in what way)? FIELDLIST diffs only for FatesColdAllVars

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

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

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).

[glemieux]

Ideally we should have a fix in for NGEET/fates#700 in prior to this update as well.

[glemieux]

Per discussion at the ctsm-fates standup and fates software engineering meeting today, I'm going to coordinate this to be integrated with NGEET/fates#1252.

To do:

• Update fates tag to sci.1.83.0_api.39.0.0
• Update FatesColdAllVars with additional variables name changes
• Merge Fix FATES electron transport variable being set prior to passing to FATES #3063 with this PR

[glemieux]

To do:

• add Missing on-the-fly built fates parameter file for test types that have a "case2" subdirectory #3097 expected failure
  - [ ] remove FatesColdElecTransJB from testlist (comment out)

Note: On second thought, I'm going to leave the new FatesColdElecTranJB test in the list as it runs. There is just nothing on the FATES end to receive it yet. As a result we'll see a DIFF once we integrate NGEET/fates#1350.

[glemieux]

aux_clm regression testing on derecho against ctsm5.3.041 is complete. All expected tests are B4B. The only differences are in the fates tests and are expected due to updating the fates tag. The fates NLCOMP differences are expected as well per #3063.

Izumi testing completed as well, but some of the baseline files were not available due to permission issues. I will retest these.

Results: /glade/u/home/glemieux/scratch/ctsm-tests/tests_pr3085-auxclm

[glemieux]

aux_clm regression testing in izumi against ctsm5.3.040 is complete and all expected tests are b4b. Per the CTSM SE meeting today, it was recommended to test against this previous tag as the ctsm5.3.041 tag has some tests with permission restrictions. Since 041 is the b4b-dev merge, there should be consistency with 040.

Note that the only diffs are in FATES tests, which are expected due to the fates tag updates to science and the NLCOMP diff due to #3063.

Results: /scratch/cluster/glemieux/ctsm-tests/tests_0508-100725iz

UPDATE: I realized there are two fates tests that didn't get checked against baseline due to permission restrictions in ctsm5.3.040:

SMS_Ld10_D_Mmpi-serial.CLM_USRDAT.I1PtClm60Fates.izumi_nag.clm-FatesFireLightningPopDens--clm-NEON-FATES-NIWO
SMS_Ld10_D_Mmpi-serial.CLM_USRDAT.I1PtClm60Fates.izumi_nag.clm-FatesPRISM--clm-NEON-FATES-YELL

[glemieux]

UPDATE: I realized there are two fates tests that didn't get checked against baseline due to permission restrictions in ctsm5.3.040:

SMS_Ld10_D_Mmpi-serial.CLM_USRDAT.I1PtClm60Fates.izumi_nag.clm-FatesFireLightningPopDens--clm-NEON-FATES-NIWO
SMS_Ld10_D_Mmpi-serial.CLM_USRDAT.I1PtClm60Fates.izumi_nag.clm-FatesPRISM--clm-NEON-FATES-YELL

I realized that these are actually expected RUN failures and not problems with the permission, which is why the baselines are not available:

CTSM/cime_config/testdefs/ExpectedTestFails.xml

Lines 188 to 208 in e0104b9

	<test name="SMS_Ld10_D_Mmpi-serial.CLM_USRDAT.I1PtClm60Fates.izumi_nag.clm-FatesFireLightningPopDens--clm-NEON-FATES-NIWO">
	<phase name="SHAREDLIB_BUILD">
	<status>FAIL</status>
	<issue>#2310</issue>
	</phase>
	<phase name="RUN">
	<status>FAIL</status>
	<issue>#2310</issue>
	</phase>
	</test>
	<test name="SMS_Ld10_D_Mmpi-serial.CLM_USRDAT.I1PtClm60Fates.izumi_nag.clm-FatesPRISM--clm-NEON-FATES-YELL">
	<phase name="SHAREDLIB_BUILD">
	<status>FAIL</status>
	<issue>#2310</issue>
	</phase>
	<phase name="RUN">
	<status>FAIL</status>
	<issue>#2310</issue>
	</phase>
	</test>

@adrifoster I'll update the change log and this should be good to go.