Add post processing with UPP to runtime

[fossell]

Expected Differences

• [x] Do these changes modify the system output in any way? [No]
  These changes add UPP grib2 output files, they do not change existing output.

Pull Request Testing

• [x] Describe testing already performed for these changes:
  The test case was performed on the AWS cluster and with just a couple forecast hours, e.g. editing test.yml enddate to only process two forecast hours. Grib files were transferred to local machine and inspected with wgrib2 utility to ensure valid data is being produced.

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

  wrfcloud-cluster create
  wrfcloud-cluster connect
  git clone https://github.com/NCAR/wrfcloud -b feature-51/add_upp_script
  cd wrfcloud/python/src/
  pip3 install --user .
  export PATH="${HOME}/.local/bin/:${PATH}"
  mkdir -p /data/input_data/gfs/2022060100/
  cd /data/input_data/gfs/2022060100/
  aws s3 sync s3://wrfcloud-xfer-tmp/ .
  mkdir -p configurations/test; mv geo_em.d01.nc configurations/test
  cp ~/wrfcloud/python/src/wrfcloud/runtime/configurations/test/namelist.* configurations/test/
  cp ~/wrfcloud/python/src/wrfcloud/runtime/test.yml .
  unset I_MPI_OFI_PROVIDER

  Edit the test.yml to process just a couple fhrs, e.g.

  run:
  configuration: test
  workdir: /data/testrun
  start: 2022-06-01_06:00:00
  end: 2022-06-01_07:00:00
  input_freq_sec: 10800
  output_freq_sec: 3600

Run the system: wrfcloud-run

Successful tests should result in the ungrib, metgrid, real, wrf, and upp components completing as normal. Check the /data/testrun/upp path and fhr_* subdirectories to ensure that grib files (WRFPRS.Grb.FXX) exist and are non-zero. Further inspection can be done by scp-ing one of the grib files to local machine and using wgrib2 to inspect the file, but not required at this point. In the future, might be nice to have wgrib2 installed in the AMI for development work.

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

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

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

• [ ] Please complete this pull request review by [October 7, 2022].
  

Pull Request Checklist

• [x] Review the source issue metadata (labels, project, and milestone).
• [x] Complete the PR definition above.
• [x] Ensure the PR title matches the feature or bugfix branch name.
• [x] Define the PR metadata, as permissions allow. Select: Reviewer(s) Select: Project Select: Milestone as the version that will include these changes Select: Development to link to the original development issue.
• [ ] 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.

[fossell]

@hahnd @mkavulich - I committed your suggested changes and tested them, all works as expected. Please review again and approve if ready.

[fossell]

@mkavulich - I took all your suggestions, David approved, so I merged so I can work on the next piece. If you have any pressing issues with these mods please let me know.