Stop using cached seba data

[frode-aarstad]

Issue
Resolves #9515

Approach
Short description of the approach

(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 91.89%. Comparing base (4301b63) to head (e9e3d0f).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #9529      +/-   ##
==========================================
+ Coverage   91.86%   91.89%   +0.02%     
==========================================
  Files         433      433              
  Lines       26762    26762              
==========================================
+ Hits        24584    24592       +8     
+ Misses       2178     2170       -8     

Flag	Coverage Δ
cli-tests	39.76% <ø> (ø)
everest-models-test	34.66% <ø> (ø)
gui-tests	72.17% <ø> (+0.05%)	⬆️
integration-test	37.22% <ø> (-0.02%)	⬇️
performance-tests	52.07% <ø> (+0.10%)	⬆️
test	40.46% <ø> (ø)
unit-tests	74.14% <ø> (+<0.01%)	⬆️

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.

[verveerpj]

LGTM!