Move setting of code paths to resources/env_vars.yaml

Describe the Enhancement

Instead of creating paths to code bases (e.g. WRF, WPS, UPP, etc) in the runtime/init.py, leverage the resources/env_vars.yaml file instead.

Time Estimate

1 day

Sub-Issues

Consider breaking the enhancement down into sub-issues.

• Add a checkbox for each sub-issue here.

Relevant Deadlines

??

Define the Metadata

Assignee

• Select engineer(s) or no engineer required
• Select scientist(s) or no scientist required

Labels

• Select component(s)
• Select priority

Projects and Milestone

• Select Project
• Select Milestone as the next official version or Backlog of Development Ideas

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 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), Project, and Development issue
  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.

Start by reading runtime/init.py to trace how paths for WRF, WPS, UPP, and other code bases are created, then inspect resources/env_vars.yaml. Move the path settings to that YAML file and verify that runtime consumers still resolve the expected paths using the existing test suite.