Add support for accumulated history fields

[peverwhee]

Tag name (required for release branches): TBD
Originator(s): peverwhee
AI tools used (if applicable; please also add the "AI-generated code" label to the PR): n/a
What:
How:

Description (include the issue title, and the keyword ['closes', 'fixes', 'resolves'] followed by the issue number):

• Adds support for accumulated (min, max, stdev [var], avg) fields
• Allows for field-specific fill values (passed into add field and populated in the hist_field object)
• Incorporates changes for, when write_nstep0=true for a file, the nstep0 file is written and then immediately closed ("real" run samples not included)
• Adds logic to clobber accumulated field settings (switch to instantaneous) if the output frequency for a file is 1*nsteps (every step) - same behavior as in CAM

Describe any changes made to build system:

M  cime_config/atm_in_paramgen.py
- small bugfix for namelist parsing
M  cime_config/hist_config.py
- clobber accumulated settings if frequency is every timestep

Describe any changes made to the namelist: n/a

List any changes to the defaults for the input datasets (e.g. boundary datasets): n/a

List all files eliminated and why: n/a

List all files added and what they do: n/a

List all existing files that have been modified, and describe the changes:
(Helpful git command: git diff --name-status development...<your_branch_name>)

M  .gitmodules
M  src/history/buffers
- bring in latest history external

M  src/history/cam_hist_file.F90
- add new reset_samples function; clear the buffers after writing to file
- get norm value with real64 buffer, then set to real32 before writing (if applicable)
- add missing error handling

M  src/history/cam_history.F90
- don't clear the buffers for every file every timestep! obviously!
- pass fill_value to file object
- modify logic to handle nstep0 writing (to it's own file)
- add missing error handling

If there are new failures (compared to the test/existing-test-failures.txt file),
have them OK'd by the gatekeeper, note them here, and add them to the file.
If there are baseline differences, include the test and the reason for the
diff. What is the nature of the change? Roundoff?

derecho/intel/aux_sima:

SMS_Ln9.mpasa120_mpasa120.FKESSLER.derecho_intel.cam-outfrq_kessler_mpas_derecho_history (Overall: DIFF)
SMS_Ln9.mpasa480_mpasa480.FKESSLER.derecho_intel.cam-outfrq_kessler_mpas_derecho (Overall: DIFF)
SMS_Ln9.ne3pg3_ne3pg3_mg37.FADIAB.derecho_intel.cam-outfrq_se_cslam (Overall: DIFF)
SMS_Ln9.ne3pg3_ne3pg3_mg37.FCAM7.derecho_intel.cam-outfrq_se_cslam_analy_ic (Overall: DIFF)
SMS_Ln9.ne3pg3_ne3pg3_mg37.FHS94.derecho_intel.cam-outfrq_se_cslam (Overall: DIFF)
SMS_Ln9.ne3pg3_ne3pg3_mg37.FKESSLER.derecho_intel.cam-outfrq_se_cslam (Overall: DIFF)
SMS_Ln9.ne3pg3_ne3pg3_mg37.FKESSLER.derecho_intel.cam-outfrq_se_cslam_multitape (Overall: DIFF) 
SMS_Ln9.ne3pg3_ne3pg3_mg37.FTJ16.derecho_intel.cam-outfrq_se_cslam (Overall: DIFF)
- all tests with write_nstep0=true are DIFF because of the new nstep0 behavior. Manually confirmed that answers have not changed.

SMS_Ln9.mpasa480_mpasa480.FKESSLER.derecho_intel.cam-outfrq_kessler_mpas_derecho_history (Overall: DIFF)
- new test; new baseline- 

derecho/gnu/aux_sima:

SMS_Ln2.ne3pg3_ne3pg3_mg37.FPHYStest.derecho_gnu.cam-outfrq_dme_adjust_derecho (Overall: DIFF) 
SMS_Ln2.ne3pg3_ne3pg3_mg37.FPHYStest.derecho_gnu.cam-outfrq_held_suarez_derecho (Overall: DIFF) 
SMS_Ln2.ne3pg3_ne3pg3_mg37.FPHYStest.derecho_gnu.cam-outfrq_kessler_derecho (Overall: DIFF) 
SMS_Ln2.ne3pg3_ne3pg3_mg37.FPHYStest.derecho_gnu.cam-outfrq_tj2016_after_coupler_derecho (Overall: DIFF)
SMS_Ln2.ne3pg3_ne3pg3_mg37.FPHYStest.derecho_gnu.cam-outfrq_tj2016_before_coupler_derecho (Overall: DIFF)
SMS_Ln9.mpasa480_mpasa480.FKESSLER.derecho_gnu.cam-outfrq_kessler_mpas_derecho (Overall: DIFF)
SMS_Ln9.ne3pg3_ne3pg3_mg37.FADIAB.derecho_gnu.cam-outfrq_se_cslam (Overall: DIFF)
SMS_Ln9.ne3pg3_ne3pg3_mg37.FCAM7.derecho_gnu.cam-outfrq_se_cslam_analy_ic (Overall: DIFF)
SMS_Ln9.ne3pg3_ne3pg3_mg37.FHS94.derecho_gnu.cam-outfrq_se_cslam (Overall: DIFF)
SMS_Ln9.ne3pg3_ne3pg3_mg37.FKESSLER.derecho_gnu.cam-outfrq_se_cslam (Overall: DIFF)
SMS_Ln9.ne3pg3_ne3pg3_mg37.FTJ16.derecho_gnu.cam-outfrq_se_cslam (Overall: DIFF)
- all tests with write_nstep0=true are DIFF because of the new nstep0 behavior. Manually confirmed that answers have not changed.

SMS_Ln9.mpasa480_mpasa480.FKESSLER.derecho_gnu.cam-outfrq_kessler_mpas_derecho_history (Overall: DIFF)
- new test; new baseline

derecho/nvhpc/aux_sima: run via github workflow

If this changes climate describe any run(s) done to evaluate the new
climate in enough detail that it(they) could be reproduced:

CAM-SIMA date used for the baseline comparison tests if different than latest:

[nusbaume]

Thanks for bringing in the new history accumulation features (and fixing some bugs) @peverwhee! I have some questions and change requests, but if you run into problems with any of them then just let me know. Thanks again!

[nusbaume]

Thanks for addressing my concerns @peverwhee! I had two remaining cleanup requests, but after that we should be good to go. Thanks again!

[nusbaume]

Why have this REAL32 check here at all? It looks like the allocate statements are now exactly the same.

[nusbaume]

Same question here, is this if-statement needed anymore?