Add Forcing Engine CI/CD Job and Realization Config Option

[program--]

This PR resolves #762 and resolves #763.

Additions

• Adds test_forcing_engine_integration to module integrations. This job runs the test_forcings_engine unit test executable.
• Adds a branch in Formulation_Constructors for a ForcingEngine option. Currently, this throws a runtime error.

Todos

• Depends on Forcings Engine Data Provider Interface and Lumped Forcings Implementation #720.
• Implement full logic for constructing a forcing engine data provider.
• Determine best approach for required GRIB files. (i.e. store in repo, extract on-demand, etc.)

Checklist

• PR has an informative and human-readable title
• Changes are limited to a single goal (no scope creep)
• Code can be automatically merged (no conflicts)
• Code follows project standards (link if applicable)
• Passes all existing automated tests
• Any change in functionality is tested
• New functions are documented (with a description, list of inputs, and expected output)
• Placeholder code is flagged / future todos are captured in comments
• Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)
• Reviewers requested with the Reviewers tool ➡️

Target Environment support

• Linux
• macOS

[PhilMiller]

Git-LFS could be good for this.
https://docs.github.com/en/repositories/working-with-files/managing-large-files/about-git-large-file-storage

[PhilMiller]

Or, we could do the testing with very cut-down files that will fit in the repo more nicely.

[program--]

Yeah those are the same two options I was considering -- I'm leaning toward creating cut down files and creating a simple domain