fix(stream): resume connection when stream errors or is destroyed

[wellwelwel]

This PR continues #3769 work and fixes #3596. It also seems to resolve #1847 and resolve #1168, ensuring that destroy and error events are properly issued (not using try-catch, but stream.on('error', () => {}) approach, which is the expected pattern for callbacks).

---

In #3769, it destroys the connection on error to ensure that the stack is not blocked, but this approach can be aggressive, as a query error shouldn't destroy the connection.

In this PR, the approach is to destroy the current stream itself on error and emits the appropriate events, ensuring its functionality and allowing users to catch errors that were not previously emitted, as reported in #1847.

---

Before this PR

The test that checks the events is not reached and the script is silently ended prematurely:

After this PR

Now all tests are reached:

---

Note

Thanks @fenichelar, @CarlOlson, and @dsech. Your examples and solutions helped us achieve a better understanding of the error 🤝

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.23%. Comparing base (69c1122) to head (fb8dbba).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #3775      +/-   ##
==========================================
+ Coverage   89.20%   89.23%   +0.03%     
==========================================
  Files          86       86              
  Lines       13549    13583      +34     
  Branches     1576     1585       +9     
==========================================
+ Hits        12086    12121      +35     
+ Misses       1463     1462       -1     

Flag	Coverage Δ
compression-0	89.23% <100.00%> (+0.03%)	⬆️
compression-1	89.23% <100.00%> (+0.03%)	⬆️
static-parser-0	86.80% <100.00%> (+0.04%)	⬆️
static-parser-1	87.57% <100.00%> (+0.03%)	⬆️
tls-0	88.65% <100.00%> (+0.03%)	⬆️
tls-1	89.00% <100.00%> (+0.14%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.