fix: handle unexpected end of stream

[KATT]

• we can't know if a specific async type is done or not as it's the responsibility of the type itself
• we can know if a stream is interrupted prematurely, so I added a check for that
• we treat the "stream interrupted" as a message that we enqueue - if the interruption happens when the iterator has already consumed what it needs, we're all good

[github-actions]

PR Compliance Checks

Thank you for your Pull Request! We have run several checks on this pull request in order to make sure it's suitable for merging into this project. The results are listed in the following section.

Issue Reference

In order to be considered for merging, the pull request description must refer to a specific issue number. This is described in our Contributing Guide. We are closing this pull request for now but you can update the pull request description and reopen the pull request.
The check is looking for a phrase similar to: "Fixes #XYZ" or "Resolves #XYZ" where XYZ is the issue number that this PR is meant to address.

[codecov]

Codecov Report

Attention: 10 lines in your changes are missing coverage. Please review.

Files	Coverage Δ
src/async/asyncTypes.ts	100.00% <100.00%> (ø)
src/async/deserializeAsync.ts	97.80% <100.00%> (-1.28%)	⬇️
src/async/handlers/tsonAsyncIterable.ts	100.00% <100.00%> (+11.66%)	⬆️
src/async/serializeAsync.ts	96.40% <100.00%> (-0.02%)	⬇️
src/errors.ts	100.00% <ø> (+16.36%)	⬆️
src/index.ts	100.00% <100.00%> (ø)
src/internals/testUtils.ts	95.65% <100.00%> (+1.05%)	⬆️
src/async/handlers/tsonPromise.ts	92.95% <76.47%> (-1.96%)	⬇️
src/async/asyncErrors.ts	86.36% <86.36%> (ø)

📢 Thoughts on this report? Let us know!.

[KATT]

I'd like to get rid of this try/catch 🤷

[KATT]

We don't clear the cache because stuff can be listening