Feature #2532 tc_winds

[JohnHalleyGotway]

Expected Differences

If the full circle (AL) winds are not defined in the ATCF input, automatically derive them from the non-zero quadrant values. Note that these changes would NOT handle a case where both the 34-kt (for example) "full circle" winds and "quadrant" winds are defined on different ATCF lines. But I've never actually seen that in reality and don't think that it exists.

• 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:
  
  Manually ran unit_tc_pairs.xml and observed the updated values in the A/BAL_WIND_34, A/BAL_WIND_50, and A/BAL_WIND_64 output columns.

• Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:
  
  Make sure all the GHA tests run and that the only diffs are based on changes to the TCMPR columns listed 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]
  No new tests needed.

• Will this PR result in changes to the test suite? [Yes]
  
  If yes, describe the new output and/or changes to the existing output:
  
  Will change the content of the A/BAL_WIND_34, A/BAL_WIND_50, and A/BAL_WIND_64 output columns from NA to some valid data values.

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

[KathrynNewman]

Looks good. Differences were contained to the A/BAL_WIND_34, A/BAL_WIND_50 and A/BAL_WIND_64 columns.

[JohnHalleyGotway]

Thanks @KathrynNewman for the review! Merging these changes now.