Add everest to rapid tests

[eivindjahren]

The additional time taken is ~5s due to xdist.

• 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 auto --hypothesis-profile=fast -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

[jonathan-eq]

LGTM! 🚢

[codspeed-hq]

CodSpeed Performance Report

Merging #9831 will degrade performances by 14%

_{Comparing eivindjahren:add_everest_to_rapid_tests (1ff21be) with main (3f61abe)}

Summary

❌ 1 regressions
✅ 23 untouched benchmarks

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

Benchmarks breakdown

	Benchmark	main	eivindjahren:add_everest_to_rapid_tests	Change
❌	test_direct_dark_performance_with_storage[gen_x: 20, sum_x: 20 reals: 10-gen_data-get_record_observations]	1.3 ms	1.5 ms	-14%