Trust the queue system when a job is finished in tests

[berland]

This avoids always spending 120 billable cpu-seconds on every test. Instead we trust that the queue system is correct when it claims a job is finished, instead of waiting it out.

Issue
Resolves overspending of github action runners.

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 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

[codspeed-hq]

CodSpeed Performance Report

Merging #9812 will not alter performance

_{Comparing berland:dontwaitkilltest (3eb19a7) with main (fd06848)}

Summary

✅ 24 untouched benchmarks

[eivindjahren]

⏲️ 💵