Feature #2168 tc_diag

[JohnHalleyGotway]

This introduces the first version of the TC-Diag tool. This initial version is limited in functionality and only actually writes gridded NetCDF output in cylindrical coordinates. It does NOT actually compute TC diagnostics yet, but will do so in MET version 12.0.0.

Expected Differences

• Do these changes introduce new tools, command line arguments, or configuration file options? [Yes]
  
  If yes, please describe:
  
  Adds new TC-Diag tool.

• 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 new NetCDF output from TC-Diag in cylindrical coordinates. It is pretty similar to the output from TC-RMW.

Pull Request Testing

• Describe testing already performed for these changes:
  

Tested extensively during development.

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

Review code changes.
Review doc updates - although the actual doc contents will be updated by #2558.
Inspect the new output from the new unit_tc_diag.xml test.
Run on the command line and note the warning message about the "beta status".

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

While this does introduce a new TC-Diag chapter, I will review/revise it with #2558.

• Do these changes include sufficient testing updates? [Yes]

Yes, for now. We will want to add new tests and/or modify the existing one after the TC-Diag tool is more complete.

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

Adds new output from unit_tc_diag.xml.

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

[jvigh]

@JohnHalleyGotway I have finished reviewing all of the code changes. They look good to me. I just left a few clarification questions and spotted a misspelling in one spot. This development represents a ton of work. Good job at getting this part of the finish line!

[jvigh]

@JohnHalleyGotway I have left some questions/comments for clarification. I have finished checking all of the code changes. This looks very good. It represents a ton of work, so congratulations on getting this first phase of the TCDiag tool across the finish line. !

[jvigh]

Sorry for the duplicate messages. I thought perhaps I had not done my review correctly, but now I just see that it adds it to the conversation.

[JohnHalleyGotway]

Thanks for the review @jvigh. Proceeding with merging these changes.