Replace server_started Event with Future to handle exceptions

[xjules]

Issue
In a very special case zmq server might fail during initialization and all occurrences of server_started.wait() will wait indefinitely and therefore replacing it with asyncio.Future which provides additional exception trigger.

Approach
Short description of the approach

(Screenshot of new behavior in GUI if applicable)

• 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 #9749 will not alter performance

_{Comparing xjules:zmq_server_start (24635d0) with main (0b80ac1)}

Summary

✅ 24 untouched benchmarks

[jonathan-eq]

Very good!