Limit the use of EverestConfig in function signatures in everest csv exporting

[DanSava]

Issue
Resolves #9162

• 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.75%. Comparing base (4b18368) to head (2622c1b).
Report is 4 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #9163      +/-   ##
==========================================
- Coverage   90.76%   90.75%   -0.01%     
==========================================
  Files         351      351              
  Lines       21901    21903       +2     
==========================================
  Hits        19879    19879              
- Misses       2022     2024       +2     

Flag	Coverage Δ
cli-tests	39.25% <ø> (+0.01%)	⬆️
gui-tests	71.74% <ø> (-0.01%)	⬇️
performance-tests	49.39% <ø> (+<0.01%)	⬆️
unit-tests	79.64% <ø> (-0.03%)	⬇️

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.