Feature #2366 pyembed_winds

[JohnHalleyGotway]

This PR includes the following changes:

1. Enable the level string to be defined for python embedding and stored in VarInfo::LevelInfo::ReqName. This is useful when finding U/V matches.
2. Refine the Point-Stat and Grid-Stat logic when searching for U/V matches. Only check that the level strings match if at least one of them is non-empty.
3. Print DEBUG(3) log message to list out which U/V fields array entries match.
   Should I include the magic string (i.e. name/level) in the log message or is the number sufficient?

DEBUG 3: U-wind field array entry 1 matches V-wind field array entry 2.
DEBUG 3: V-wind field array entry 2 matches U-wind field array entry 1.

4. Print DEBUG(3) log message when U/V matches are not found.

DEBUG 3: U-wind field array entry 3 has no matching V-wind field array entry.
DEBUG 3: V-wind field array entry 4 has no matching U-wind field array entry.

5. Print WARNING message is multiple U/V matches are found.
   Should this WARNING actually be an error?

DEBUG 3: U-wind field array entry 1 matches V-wind field array entry 2.
DEBUG 3: U-wind field array entry 1 matches V-wind field array entry 4.
WARNING: 
WARNING: GridStatConfInfo::process_config() -> For U-wind, found multiple matching V-wind field array entries! Set the "level" strings to differentiate between them.
WARNING: 

Expected Differences

• Do these changes introduce new tools, command line arguments, or configuration file options? [No]
  
  If yes, please describe:
  
  While there's no NEW config file option, it does allow the level string to be defined for python embedding.

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

• Tested Grid-Stat with python embedding for both fcst/obs to get successful runs and trigger Debug/Warning messages.

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

• Review the code changes.

• Ensure all GHA runs pass and produce no diffs.

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

• Do these changes include sufficient testing updates? [Yes or No]
  No new unit tests added.

• 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 [Wed 12/7/22].
  

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

@georgemccabe based on our discussion on 12/6/22, I made the changes seen in these 2 commits:

• add is_req_level_match() utility function
• add a python embedding unit test

Note that this will change the contents of an existing output file from the unit tests and will be flagged as a difference.

[georgemccabe]

These changes look good. @JohnHalleyGotway and I met briefly yesterday to discuss the changes. John made some adjustments based on our conversation to reduce duplicate logic and added a unit test to ensure that the new functionality works as expected. The only failed check is due to new output data being generated from the changes to the unit tests.

The truth data will need to be updated after this PR is merged. I approve.