fix: Destroying execution environment streams should emit events

[FrederikBolding]

Previously we would remove event listeners when calling destroy. This meant that consumers of our streams would not be notified that the stream was closed causing issues like Cannot call write after a stream was destroyed.

Instead, we want consumers to be notified when a stream is torn down. One issue however is that it introduces new issues where some code paths throw Premature close. This seems to be an underlying problem in the MetaMask stream architecture and the error message is ignored on the extension client. We do the same here.

This will eventually also allow us to remove closeConnections from the SnapController constructor.

[codecov]

Codecov Report

❌ Patch coverage is 80.00000% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 98.29%. Comparing base (6cea1bf) to head (87a111b).
⚠️ Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
...cution-environments/src/common/BaseSnapExecutor.ts	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3074      +/-   ##
==========================================
+ Coverage   98.27%   98.29%   +0.02%     
==========================================
  Files         417      417              
  Lines       11759    11759              
  Branches     1827     1827              
==========================================
+ Hits        11556    11559       +3     
+ Misses        203      200       -3     

☔ 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.

[Mrtenz]

Wondering if we should still check !stream.destroyed here?

[FrederikBolding]

I thought I had found evidence that you could call it multiple times without issue, but I can't find it now. Will just re-add the check