add 2 diags z* coords and diag_table updates, fixes #133

[raphaeldussin]

This PR defines 2 diagnostics z* coords (33 levels for global, 40 level for regional). Adding global field in 33 z* in diag_tables + placeholder for regional output (example for US east, not tested)

[sanAkel]

@raphaeldussin
RTOFS v2.5 provides 3d files in the following 3 regions (sample files are linked; if you happen to read this note 2-days after 2026/05/23, please adjust URL accordingly):

1. US_east
2. US_west
3. Alaska

My gut feeling is that it is probably cheaper to write 6-hourly global files and cut out (via post processing) for the above 3 regions instead of writing (via diag_table) for each region, e.g., "-105.19 -40.72 0.0 79.75" as you have it.

Am I wrong or we should test the 2 approaches?

[raphaeldussin]

@sanAkel my preference would be to let MOM remap from native to 40 levels using ALE for the regions instead of doing a vertical remap from the 33 levels of the global to 40 levels, in which we don't add more information. In terms of cost, we have to test both and decide.

Feel free to merge this PR to test the global z output. I need to do further testing to make sure the regions are lining up with RTOFS2.5 once I have a working config. I will then create a new PR with the updated/validated region outputs.