Bugfix #2514 develop clang

[JohnHalleyGotway]

Expected Differences

This PR proposes the same changes #2556, but for the develop branch rather than main_v11.0. Thanks to @srherbener for proposing this fix!

• 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 locally using GNU to confirm that it all still compiles well. I do NOT have a Clang development environment set up. Recommend requesting that @srherbener compile the MET-11.1.0-rc1 release in his Clang environment to confirm that MET-11.1.0 won't introduce any new Clang issues. Longterm, we should automate the Clang testing via GHA.

• Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:
  
  Confirm that the code compiles well. Note that recently approved PR's will likely trigger diffs in the output, but that's unrelated to these changes.

• Do these changes include sufficient documentation updates, ensuring that no errors or warnings exist in the build of the documentation? [No]
  No doc updates made or needed at this point. If/when we automate Clang compilation testing via GHA, recommend updating the user's guide to state that support.

• Do these changes include sufficient testing updates? [No]
  None needed.

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

• Please complete this pull request review by [Friday 6/9/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.

[JohnHalleyGotway]

GHA compiled these changes fine and ran the unit tests with no diffs. Proceeding with merging this PR.