Feature 1482 use case buoy data

[j-opatz]

• Describe testing already performed for these changes:
  Use case was tested to run with data, documentation was reviewed for accuracy.

• Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:
  Take a look at the documentation here:https://metplus.readthedocs.io/en/feature_1482_usecase_buoydata/generated/model_applications/marine_and_cryosphere/PointStat_fcstGFS_obsNDBC_WaveHeight.html#sphx-glr-generated-model-applications-marine-and-cryosphere-pointstat-fcstgfs-obsndbc-waveheight-py
  Check automated tests that only difference is the new output
  Optional: run the use case. Data is on Seneca, under /d1/personal/jopatz/model_applications.

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

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

• Please complete this pull request review by [Fill in date].
  11/07

Pull Request Checklist

See the METplus Workflow for details.

• Add any new Python packages to the METplus Components Python Requirements table.
• 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.

[hankenstein2]

Reviewed documentation and ran the use case on seneca, got identical results and everything looks good. All github action tests came back successful except the expected failure of a directory missing the new data.