Feature update modulefiles

[jprestop]

Pull Request Testing

• [x] Describe testing already performed for these changes:
  I tested loading these new modulefiles on the various machines.

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

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

• [x] Do these changes include sufficient testing updates? [N/A]

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

• [x] Do these changes introduce new SonarQube findings? [No]
  If yes, please describe:

• [x] Please complete this pull request review by [20240503].
  

Pull Request Checklist

See the METplus Workflow for details.

• [x] Add any new Python packages to the METplus Components Python Requirements table.
• [No issue] Review the source issue metadata (required labels, projects, 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: Organization level software support Project or Repository level development cycle Project Select: Milestone as the version that will include these changes
• [No issue] After submitting the PR, select the :gear: icon in the Development section of the right hand sidebar. Search for the issue that this PR will close and select it, if it is not already selected.
• [ ] 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.

[coveralls]

Pull Request Test Coverage Report for Build 9003284096

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 90.947%

---

Totals
Change from base Build 8834576323:	0.0%
Covered Lines:	8599
Relevant Lines:	9455

---

💛 - Coveralls