Be able to handle point output if point/grid mismatch because -180 to 180 vs 0 to 360

[JessicaMeixner-NOAA]

Is your feature request related to a problem? Please describe.
As reported by @NickSzapiro-NOAA here: ufs-community/ufs-weather-model#2368

One can run into issues where point output and the grids do not match because they are defined by -180 to 180 vs 0 to 360 for one or the other.

Describe the solution you'd like
Solutions posed by @NickSzapiro-NOAA here: ufs-community/ufs-weather-model#2368

• modifying the (non-polar) longitudes in parm/ww3_points.list
• enhancing the internals used in W3IOPP to preprocess point output (or for unstructured grids in: https://github.com/NOAA-EMC/WW3/blob/develop/model/src/w3triamd.F90#L1604)

Describe alternatives you've considered

While the first solution is a great immediate solution, ideally we should enhance WW3 so that this is a non-issue.

Additional context
Add any other context or screenshots about the feature request here.

[JessicaMeixner-NOAA]

FYI - Starting to work on this, by updating https://github.com/NOAA-EMC/WW3/blob/develop/model/src/w3triamd.F90#L1604

[JessicaMeixner-NOAA]

Branch with potential fix is here: https://github.com/JessicaMeixner-NOAA/WW3/tree/bug/points180360 working to confirm that differences in standalone WW3 regression tests are as expected and testing in GFS set-up before submitting PR.

[DeniseWorthen]

@JessicaMeixner-NOAA Is this updated in the dev/ufs-weather-model branch yet?

[JessicaMeixner-NOAA]

Not yet... should be next commit after the next batch which is all non-answer changing though. That PR should be submitted to UFS using this WW3 PR #1381 soon and I'm already working on the PR for this bug fix to follow, which is the next commit in develop.