Global UtilityRoutines

[mitchute]

Pull request overview

• Moves UtilityRoutines data to state
• ShowSevereError, ShowContinueError, and all other similar error or message methods are affected.

Pull Request Author

Add to this list or remove from it as applicable. This is a simple templated set of guidelines.

• Title of PR should be user-synopsis style (clearly understandable in a standalone changelog context)
• Label the PR with at least one of: Defect, Refactoring, NewFeature, Performance, and/or DoNoPublish
• Pull requests that impact EnergyPlus code must also include unit tests to cover enhancement or defect repair
• Author should provide a "walkthrough" of relevant code changes using a GitHub code review comment process
• If any diffs are expected, author must demonstrate they are justified using plots and descriptions
• If changes fix a defect, the fix should be demonstrated in plots and descriptions
• If any defect files are updated to a more recent version, upload new versions here or on DevSupport
• If IDD requires transition, transition source, rules, ExpandObjects, and IDFs must be updated, and add IDDChange label
• If structural output changes, add to output rules file and add OutputChange label
• If adding/removing any LaTeX docs or figures, update that document's CMakeLists file dependencies

Reviewer

This will not be exhaustively relevant to every PR.

• Perform a Code Review on GitHub
• If branch is behind develop, merge develop and build locally to check for side effects of the merge
• If defect, verify by running develop branch and reproducing defect, then running PR and reproducing fix
• If feature, test running new feature, try creative ways to break it
• CI status: all green or justified
• Check that performance is not impacted (CI Linux results include performance check)
• Run Unit Test(s) locally
• Check any new function arguments for performance impacts
• Verify IDF naming conventions and styles, memos and notes and defaults
• If new idf included, locally check the err file and other outputs

[mitchute]

@Myoldmopar CI is happy here. Let me know if you need anything else on this PR.

[Myoldmopar]

I don't have any additional comments. CI is super happy. Let me just go line by line and check all the changes real quick.

[Myoldmopar]

OK checked every changed line and confirmed they are all good.

...

OK, but for real, just going to lean pretty heavily on CI here. If something was wrong, it definitely would've been identified. And look at that, even Windows files are all happy.

Gotta get this in before it lingers. This should be the last big one though, right? 🙃

Thanks @mitchute