Only use logger.exception for unexpected exceptions

[eivindjahren]

Only use logger.exception for unexpected exceptions

• 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

[andreas-el]

💯

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 22.22222% with 7 lines in your changes missing coverage. Please review.

Project coverage is 90.81%. Comparing base (e561119) to head (db2c2ba).

Files with missing lines	Patch %	Lines
src/ert/gui/tools/plot/plot_window.py	0.00%	5 Missing ⚠️
src/ert/__main__.py	50.00%	2 Missing ⚠️

Additional details and impacted files

@@               Coverage Diff                @@
##           version-10.3    #8875      +/-   ##
================================================
- Coverage         90.81%   90.81%   -0.01%     
================================================
  Files               342      342              
  Lines             20967    20965       -2     
================================================
- Hits              19041    19039       -2     
  Misses             1926     1926              

Flag	Coverage Δ
gui-tests	75.63% <11.11%> (-0.01%)	⬇️
integration-tests	53.76% <11.11%> (-0.01%)	⬇️
unit-tests	68.78% <22.22%> (-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.