test: increase delay in workaround for flaky unit test

[reubenmiller]

Proposed changes

Increase the delay in the workaround due to (#3021), after the following CI run failure was detected:

• https://github.com/thin-edge/thin-edge.io/actions/runs/10159135440/job/28092696086?pr=3025

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
• Documentation Update (if none of the other choices apply)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue

• flaky unittest: bridge_reconnects_successfully_after_local_connection_interrupted #3021

Checklist

• I have read the CONTRIBUTING doc
• I have signed the CLA (in all commits with git commit -s)
• I ran cargo fmt as mentioned in CODING_GUIDELINES
• I used cargo clippy as mentioned in CODING_GUIDELINES
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

Further comments

[github-actions]

Robot Results

✅ Passed	❌ Failed	⏭️ Skipped	Total	Pass %	⏱️ Duration
486	0	2	486	100	1h18m15.550296s

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.1%. Comparing base (e7c43aa) to head (4d46c4d).
Report is 3 commits behind head on main.

Additional details and impacted files

see 3 files with indirect coverage changes

[reubenmiller]

we'll have to change strategy here, as the test is still failing sporadically. Once #3027 is merged, I will rebase this PR, and configure the retries feature to retry the problematic test several times.

[reubenmiller]

Closing PR as the test has been marked for retries when run using cargo-nextest. #3027