Enhance TC-RMW to better support NetCDF input files

[JohnHalleyGotway]

Describe the Enhancement

This issue arose from discussion dtcenter/METplus#3283 in which @mpm-meto encountered challenges running MET's TC-RMW tool using NetCDF inputs. Testing for that issue revealed some enhancements that could make running TC-RMW using NetCDF inputs easier. For this issue, recommend the following changes:

1. Add a unit test for TC-RMW demonstrating the use of NetCDF inputs.
2. Add more error checking to prevent TC-RMW from attempting to write to 4D data to a 3D variable. That resulted in corrupted output rather than a useful error message.
3. Consider if/how writing VR and VT for a single level should be supported. Currently TC-RMW only supports VR and VT for multiple pressure level outputs.
4. Investigate and resolve the writing of some "false positive" warning messages, like this:

WARNING: MetNcCFDataFile::data_plane(VarInfo &, DataPlane &, LongArray &) -> for "x_wind_0" variable, the lead time does not match the requested lead time: (240000 != NA)

Refine the logic to prevent those from being written. When running with forecast model data and forecast tracks, yes, the lead time information should match. But when running with analysis data and BEST tracks, no, the lead times should not, and will not match. Those warning messages should be suppressed in that case.

Time Estimate

3 days?

Sub-Issues

Consider breaking the enhancement down into sub-issues.

• Add a checkbox for each sub-issue here.

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

Define the source of funding and account keys here or state NONE.

Define the Metadata

Assignee

• Select engineer(s) or no engineer required
• Select scientist(s) or no scientist required

Labels

• Review default alert labels
• Select component(s)
• Select priority
• Select requestor(s)

Milestone and Projects

• Select Milestone as a MET-X.Y.Z version, Consider for Next Release, or Backlog of Development Ideas
• For a MET-X.Y.Z version, select the MET-X.Y Development project

Define Related Issue(s)

Consider the impact to the other METplus components.

• METplus, MET, METdataio, METviewer, METexpress, METcalcpy, METplotpy

Enhancement Checklist

See the METplus Workflow for details.

• Complete the issue definition above, including the Time Estimate and Funding Source.
• Fork this repository or create a branch of develop.
  Branch name: feature_<Issue Number>_<Description>
• Complete the development and test your changes.
• Add/update log messages for easier debugging.
• Add/update unit tests.
• Add/update documentation.
• Push local changes to GitHub.
• Submit a pull request to merge into develop.
  Pull request: feature <Issue Number> <Description>
• Define the pull request metadata, as permissions allow.
  Select: Reviewer(s) and Development issue
  Select: Milestone as the next official version
  Select: MET-X.Y Development project for development toward the next coordinated release
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Close this issue.