Add warning when everest-models file outputs do not match everest objectives

[DanSava]

Issue
Resolves #8757

(Screenshot of new behavior in GUI if applicable)

• 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 unit tests pass locally after every commit (git rebase -i main --exec 'pytest tests/ert/unit_tests -n logical -m "not integration_test"')

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.69%. Comparing base (90d11ec) to head (b7f8fe8).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #9120      +/-   ##
==========================================
- Coverage   90.81%   90.69%   -0.13%     
==========================================
  Files         351      351              
  Lines       21895    21889       -6     
==========================================
- Hits        19884    19852      -32     
- Misses       2011     2037      +26     

Flag	Coverage Δ
cli-tests	39.17% <ø> (-0.07%)	⬇️
gui-tests	71.79% <ø> (+0.05%)	⬆️
performance-tests	49.42% <ø> (+0.05%)	⬆️
unit-tests	79.65% <ø> (-0.05%)	⬇️

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.