Feature #2648 mode_cts

[JohnHalleyGotway]

Expected Differences

I'm including in this pull request 4 substantive changes.
You'll see that 177 files are modified but 167 of those are just one-line config file updates.

1. Adding 7 new statistics to the end of the MODE CTS line type, as requested. This includes updates to the user's guide to list them.

• Please see changes in mode_columns.h, mode_exec.cc, and mode.rst.

2. Updating the version number in the code from 11.1.0 to 12.0.0. Since the output line types are changing, now is the time to update the version number. This includes:

• Change the version number listed in util_contstants.h.
• Add header table files for the new version in met_header_columns_v12.0.txt, met_12_0_0.hdr, update the MODE CTS columns, and update 2 Makefiles to install the new files.
• Changes to a whopping 167 configuration files! Just changing version = "V11.1.0"; to version = "V12.0.0"; in all the files named *Config*.

Unrelated to this GitHub issue, but worth noting:

3. Modify logic in testing.yml to keep it consistent with a recent PR for the main_v11.1 branch.
4. Delete .find_grid_by_name.h.swp that was inadvertently added to the repo at some point.

• Do these changes introduce new tools, command line arguments, or configuration file options? [No]
  
  If yes, please describe:
  

• Do these changes modify the structure of existing or add new output data types (e.g. statistic line types or NetCDF variables)? [Yes]
  
  If yes, please describe:
  
  Adds 7 new columns to the MODE CTS output files. Changes the version number of the MET output from 11.1.0 to 12.0.0.

Pull Request Testing

• Describe testing already performed for these changes:
  
  Ran make install and make test locally to confirm that MODE runs well. Reviewed newly generated values in the 7 new columns of the MODE CTS output and confirmed made sure they're at least reasonable.

• Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:
  
  Please review the documentation changes via RTD. Please review the substantive code changes, looking for typos and mistakes. You can basically ignore the config file changes.

• Do these changes include sufficient documentation updates, ensuring that no errors or warnings exist in the build of the documentation? [Yes]

• Do these changes include sufficient testing updates? [Yes]
  No new tests are needed since the existing set of tests already generates MODE CTS output many times.

• Will this PR result in changes to the test suite? [YES]
  
  If yes, describe the new output and/or changes to the existing output:
  
  Basically everything will change since the version number is changing from 11.1.0 to 12.0.0. That'll make the diff step very, very slow and we'll want to update the reference the develop-ref version ASAP after this PR is merged.

Please do download and view at least some of the MODE CTS difference files and confirm that the newly added stats are correct.

• Please complete this pull request review by [Tuesday 8/22/23].
  

Pull Request Checklist

See the METplus Workflow for details.

• Review the source issue metadata (required labels, projects, and milestone).
• Complete the PR definition above.
• Ensure the PR title matches the feature or bugfix branch name.
• Define the PR metadata, as permissions allow.
  Select: Reviewer(s)
  Select: Organization level software support Project or Repository level development cycle Project
  Select: Milestone as the version that will include these changes
• After submitting the PR, select the ⚙️ icon in the Development section of the right hand sidebar. Search for the issue that this PR will close and select it, if it is not already selected.
• After the PR is approved, merge your changes. If permissions do not allow this, request that the reviewer do the merge.
• Close the linked issue and delete your feature or bugfix branch from GitHub.

[j-opatz]

Changes were checked for spelling errors and consistency, with everything appearing OK. config files were not reviewed given it was a version number update.