⚡️ Improve multiple timeout tests

[AlexV525]

• Further try ✅ Fix download stream tests #2140, using drip to control the overall response duration.
• Make cancellation calls only after the response stream has been obtained to keep the call sequence.
• Using the non-routable URL (10.0.0.0) to mock connection timeouts.

New Pull Request Checklist

• I have read the Documentation
• I have searched for a similar pull request in the project and found none
• I have updated this branch with the latest main branch to avoid conflicts (via merge from master or rebase)
• I have added the required tests to prove the fix/feature I'm adding
• I have updated the documentation (if necessary)
• I have run the tests without failures
• I have updated the CHANGELOG.md in the corresponding package

[kuhnroyal]

Using drip is actually a great idea, didn't think of that!

[AlexV525]

I've updated the description, this might significantly help with random test failures.

[kuhnroyal]

Wonder if we should test the connection timeouts with mocks?

[AlexV525]

Wonder if we should test the connection timeouts with mocks?

Okay so it's not a mock, it happens because the IP is non-reachable in a regular LAN network. We should use the same URL (or something like 192.168.0.0) if we want to make sure that the connection timeouts statically happened.
Regarding the name of tests, they might also changed to non-response-related.