Less aggressive LSF

[berland]

Issue
Resolves 🔥

Approach
🕐

• 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.41%. Comparing base (5717e4d) to head (a161f0e).
Report is 9 commits behind head on version-11.0.

Additional details and impacted files

@@               Coverage Diff                @@
##           version-11.0    #9038      +/-   ##
================================================
- Coverage         91.50%   91.41%   -0.09%     
================================================
  Files               343      343              
  Lines             21276    21335      +59     
================================================
+ Hits              19468    19504      +36     
- Misses             1808     1831      +23     

Flag	Coverage Δ
cli-tests	38.96% <33.33%> (-0.02%)	⬇️
gui-tests	72.43% <33.33%> (+0.01%)	⬆️
performance-tests	49.26% <33.33%> (-0.06%)	⬇️
unit-tests	79.99% <100.00%> (-0.13%)	⬇️

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.