Refactor update workflow signature

[frode-aarstad]

Issue
Resolves #9607

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

[codspeed-hq]

CodSpeed Performance Report

Merging #9688 will not alter performance

_{Comparing frode-aarstad:refactor-update-workflow-sig (b087917) with main (5a0ff5f)}

Summary

✅ 24 untouched benchmarks

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.73%. Comparing base (5a0ff5f) to head (b087917).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #9688      +/-   ##
==========================================
+ Coverage   91.72%   91.73%   +0.01%     
==========================================
  Files         426      426              
  Lines       26550    26550              
==========================================
+ Hits        24352    24356       +4     
+ Misses       2198     2194       -4     

Flag	Coverage Δ
cli-tests	39.77% <100.00%> (ø)
everest-models-test	34.15% <50.00%> (+<0.01%)	⬆️
gui-tests	74.33% <100.00%> (ø)
integration-test	37.96% <50.00%> (ø)
performance-tests	51.57% <100.00%> (ø)
test	39.49% <50.00%> (ø)
unit-tests	74.21% <100.00%> (+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.

[yngve-sk]

Looks like a good change, I think there should be one more commit propagating this change into es_update.py also, renaming analysis_config to update_settings in _es_update.py added to this PR, starting here:

        try:
            smoother_update(
                prior,
                posterior,
                analysis_config=self._update_settings, #  <----

Came another review at the same time requesting changes

[yngve-sk]

Nice, LGTM