Enhance WRF Dockerfile to allow users to supply their own files to build

[georgemccabe]

This will allow users to more easily test changes to the model.
Existing Dockerfile can be found here: https://github.com/NCAR/container-dtc-nwp/blob/main/components/wps_wrf/Dockerfile
METplus Dockerfile that contains logic to allow different approaches to obtain source code can be found here: https://github.com/dtcenter/METplus/blob/main_v5.0/internal/scripts/docker/Dockerfile

Relevant notes from meeting on 4/7/2023:

• If you want to use a custom version of WRF instead, provide instructions to point to a different local copy or different online version
• Make it an optional argument to use a different version of WRF from what’s default (the most recent public release on github)
• Do we anticipate users to commonly want to rebuild with a different source version of WRF supplied in a custom manner? - not all but should support running other than current latest public authoritative source on Github
• Getting rid of UPP step would be a high priority
• Python visualizations would be nice to have working
  • Likely will want to expand the set of plots

Describe the Enhancement

Provide a description of the enhancement request here.

Time Estimate

Estimate the amount of work required here.
Issues should represent approximately 1 to 3 days of work.

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

• Select component(s)
• Select priority
• Select requestor(s)

Projects and Milestone

• Select Repository and/or Organization level Project(s) or add alert: NEED PROJECT ASSIGNMENT label
• Select Milestone as the next official version or Future Versions

Enhancement Checklist

• 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 issues
  Select: Repository level development cycle Project for the next official release
  Select: Milestone as the next official version
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Close this issue.

[jaredalee]

Note that this issue appears to overlap significantly with #2, so they should be dealt with concurrently.