Fix race conditions when establishing SSH connections

[maxfischer2781]

This PR addresses two race conditions around SSH connections. Major changes include:

• The state of bound and connection is now handled as a single entity.

This fixes using an SSH connection before any bound has been created (#369) as well as using a bound of a previous connection. Closes #370.

[maxfischer2781]

Looks like the coverage upload of the unittests got broken by codecov/codecov-action v5.4.1.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.94%. Comparing base (58b66e0) to head (728f7fe).
Report is 11 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #371   +/-   ##
=======================================
  Coverage   98.94%   98.94%           
=======================================
  Files          55       55           
  Lines        2266     2271    +5     
=======================================
+ Hits         2242     2247    +5     
  Misses         24       24           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[giffels]

Looks like the coverage upload of the unittests got broken by codecov/codecov-action v5.4.1.

Fixed again!

[giffels]

I have added a test case, that explicitly tests the race condition in #369 and checks that no new connection is created by the second attempt.

[maxfischer2781]

Nice, thanks! I wasn't sure how to test this, your test looks very good.

[giffels]

LGTM! Thanks a lot for providing a fix. Just decide whether you like to go for a namedtuple or stay with a tuple.

[giffels]

LGTM! Thanks for your work!

[eileen-kuehn]

LGTM 👍