Allow users without equilibrium to run ert with FLOW simulator.

[DanSava]

Issue
Resolves #8223

Approach
Create flow_config.yml config file if it is not found in the env variables.

• PR title captures the intent of the changes, and is fitting for release notes.
• Added appropriate release note label
• Commit history is consistent and clean, in line with the contribution guidelines.
• Make sure tests pass locally (after every commit!)

When applicable

• When there are user facing changes: Updated documentation
• New behavior or changes to existing untested code: Ensured that unit tests are added (See Ground Rules).
• Large PR: Prepare changes in small commits for more convenient review
• Bug fix: Add regression test for the bug
• Bug fix: Create Backport PR to latest release

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.63%. Comparing base (221fea2) to head (3714b41).
Report is 4 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #8324      +/-   ##
==========================================
+ Coverage   90.60%   90.63%   +0.03%     
==========================================
  Files         342      342              
  Lines       20898    20906       +8     
==========================================
+ Hits        18935    18949      +14     
+ Misses       1963     1957       -6     

Flag	Coverage Δ
gui-tests	75.87% <ø> (+0.01%)	⬆️
integration-tests	54.04% <ø> (-0.04%)	⬇️
unit-tests	68.75% <ø> (+0.04%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[yngve-sk]

Thanks for your patience with the questions. I think overall this looks good, could you also add some documentation so that this new behavior is described in the docs? (The current FLOW documentation does look a bit vague tbh, so if you feel like revising it a bit more that would be great). You could just write it into the Flow ForwardModelStepPlugin @ ert/shared/hook_implementations/forward_model_steps.py

[DanSava]

could you also add some documentation so that this new behavior is described in the docs? (The current FLOW documentation does look a bit vague tbh, so if you feel like revising it a bit more that would be great). You could just write it into the Flow ForwardModelStepPlugin @ ert/shared/hook_implementations/forward_model_steps.py

I added a bit of information to ert/shared/hook_implementations/forward_model_steps.py but not very much. The behaviour this PR is adding is not new it just allows a user that has flow installed on their machine to use it without having to create their own flow_config.yml

We will need to expand on this documentation once and if we decide to support additional options. But currently without using a user-defined forward model job for flow ERT only supports the default options in a flow run.

[sondreso]

Could we also create an example in test-data/ for running with flow? (Similar to this, just a complete example people could use as a starting point) Then we could also run that example as part of our tests!

[sondreso]

Very nice 💯