Feature #2469 2023_v11.1.0

[JohnHalleyGotway]

While there are a massive number of files changed, the actual changes are very minor.

• Update the copyright date from 2022 to 2023 in the source code.
• Switch "V11.0.0" to "V11.1.0" in all the config files.
• Switch the code version in util_constants.h and docs/conf.py to 11.1.0.
• Add header table files for version 11.1.0 and update Makefile.am to install them.

##Expected Differences ##

• 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)? [No]
  
  If yes, please describe:
  

Pull Request Testing

• Describe testing already performed for these changes:
  

  • Compiled this feature branch and ran all the unit tests in seneca:/d1/projects/MET/MET_pull_requests/met-11.1.0/met-11.1.0-beta1/feature_2469/MET-feature_2469_2023_v11.1.0/internal/test_unit.
  • Copied the v11.1.0 output and renumbered it as v11.0.0 (looking for files ending with .stat, .txt, .tcst, .out, and .dump).
  • Then diffed against the nightly build output.

cd /d1/projects/MET/MET_pull_requests/met-11.1.0/met-11.1.0-beta1/feature_2469/MET-feature_2469_2023_v11.1.0
internal/test_unit/bin/comp_dir.sh test_output_V11.0.0 /d1/projects/MET/MET_regression/develop/NB20230226/MET-develop/test_output >& comp_dir.log

Checking the diffs in comp_dir.log, I see NO DIFFERENCES flagged.

• Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:
  

  • Confirm that all GHA tests run without error.
  • The difference comparison step will time out. Since a simple file diff does not suffice with a version diff present, the comparison step will take too long and time out.
  • See the comp_dir.log file referenced above.

• 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]

• Will this PR result in changes to the test suite? [Yes]
  
  If yes, describe the new output and/or changes to the existing output:
  

• Please complete this pull request review by [Mon 2/27/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 Development issue with the original issue number.
• 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.

[jprestop]

I reviewed the GHA tests and saw that 22 were successful, 2 were cancelled, and 10 were skipped. Since the difference comparison step timed out, as suggested, I reviewed the comp_dir.log file and found no failures or errors. I approve this request.