fix(realtime): cancel timeout task if a successful response arrives

[o-santi]

What kind of change does this PR introduce?

Stop timeout_callback from being called after a successful message arrives, by canceling the task inside trigger. This is happening because the timeout_task inside the AsyncPush class wasn't being canceled, ever, so it would trigger the timeout every time. The default timeout task just logs that it timed out, so it was pretty harmless. However, this is a pretty bad bug to have.

Fixes #1297.

Additional context

Add any other context or screenshots.

[SmaugPool]

Note that the timeout also leads to calling subscribe() callback (if registered) with RealtimeSubscribeStates.TIMED_OUT state, possibly causing some reconnection loop from user code when it tries to handle the timeout (like I did). It is therefore not always as harmless as just a log.

[coveralls]

Pull Request Test Coverage Report for Build 19143493446

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 3 unchanged lines in 1 file lost coverage.
• Overall coverage increased (+0.02%) to 92.59%

---

Files with Coverage Reduction	New Missed Lines	%
src/realtime/_async/push.py	3	78.48%

Totals
Change from base Build 19043813501:	0.02%
Covered Lines:	8759
Relevant Lines:	9460

---

💛 - Coveralls