[DEFECT] General RAVEN Maintenance Updates

[dylanjm]

Thank you for the defect report

• I am using the latest version of RAVEN.
• I have read the Wiki.
• I have created a minimum, reproducible example
  that demonstrates the defect.

Defect Description

This issue can be used in reference to PRs that only make minor, non-functional changes to RAVEN's code. The expectation would be that these changes are small, do not affect any developer or user functionality, and are independent of other PRs.

A few examples of changes that would apply to this issue:

• Fixing SyntaxWarnings emitted during RAVEN runtime
• Fixing deprecation warnings from dependent library APIs
• Modifying a comment
• Raising/lowering the level of output to stdout (debug, warning, all, message, etc)
• Removing commented code
• Removing inconsequential code

Steps to Reproduce

The fix should be properly explained in any PR referencing this issue.

Expected Behavior

I imagine a good rule of thumb is that nobody would notice these changes took place.

Screenshots and Input Files

No response

OS

Linux

OS Version

No response

Dependency Manager

CONDA

For Change Control Board: Issue Review

• Is it tagged with a type: defect or task?
• Is it tagged with a priority: critical, normal or minor?
• If it will impact requirements or requirements tests, is it tagged with requirements?
• If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
• Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure

• If the issue is a defect, is the defect fixed?
• If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
• If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
• If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
• If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?