fix: deserializeAsync string chunks can split anywhere

[Sheraff]

String chunks can split the string anywhere and shouldn't be assumed to imply a new line.

This PR insures that deserializeAsync always accumulates the original string from the received chunks before splitting it into separate lines. Before this change, it was assumed that "end of chunk" means "end of line" even if the \n char wasn't in the original string.

It also adds a test in deserializeAsync that verifies it still works with weird chunk splits. Test didn't pass before this PR, passes now.

---

Sorry for the branch name / PR formatting, I haven't contributed to tRPC in a while I don't remember the conventions

[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: 2 lines in your changes are missing coverage. Please review.

Files	Coverage Δ
src/async/asyncTypes.ts	100.00% <100.00%> (ø)
src/async/deserializeAsync.ts	99.25% <93.93%> (-0.75%)	⬇️

📢 Thoughts on this report? Let us know!.