Speedup everest tests

[DanSava]

Issue
Resolves #9727
Resolves #9728

• 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 #9746 will degrade performances by 13.54%

_{Comparing DanSava:speedup-everest-tests (ae93312) with main (b6edc3b)}

Summary

❌ 3 regressions
✅ 21 untouched benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

	Benchmark	main	DanSava:speedup-everest-tests	Change
❌	test_direct_dark_performance_with_storage[gen_x: 20, sum_x: 20 reals: 10-gen_data-get_record_observations]	1.4 ms	1.6 ms	-10.49%
❌	test_direct_dark_performance_with_storage[gen_x: 20, sum_x: 20 reals: 10-gen_data_with_obs-get_record_observations]	2.4 ms	2.8 ms	-13.54%
❌	test_direct_dark_performance_with_storage[gen_x: 20, sum_x: 20 reals: 10-summary-get_record_observations]	1.2 ms	1.4 ms	-11.02%

[verveerpj]

Maybe this could be sped up a bit more by limiting the number of batch, e.g. to two?

[verveerpj]

Oh, guess not, its not running the case anyway?