fix: close streams when portforwarding is closed while copying (#23587)

[adietish]

does not fix eclipse-che/che#23587, it's only related to it.
only provides a small fix that allows port-forwarding to heal if it breaks while copying streams.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 41.66667% with 7 lines in your changes missing coverage. Please review.
✅ Project coverage is 3.55%. Comparing base (71098f6) to head (8e708ed).
⚠️ Report is 243 commits behind head on main.

Files with missing lines	Patch %	Lines
...tlin/com/redhat/devtools/gateway/openshift/Pods.kt	41.66%	4 Missing and 3 partials ⚠️

Additional details and impacted files

@@           Coverage Diff            @@
##            main    #200      +/-   ##
========================================
+ Coverage   0.00%   3.55%   +3.55%     
========================================
  Files          4      32      +28     
  Lines         26    1181    +1155     
  Branches       0     208     +208     
========================================
+ Hits           0      42      +42     
- Misses        26    1133    +1107     
- Partials       0       6       +6     

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

[azatsarynnyy]

Hi @adietish
I tested the patch by selecting File > Invalidate caches > Just Restart,
and there's a Connecting to remote host... window that stays forever:

If I understand correctly, it should reconnect the IDE.

[adietish]

@azatsarynnyy: This PR is only a small fix for the port forwarding (Commit 1, eclipse-che/che#23587 (comment)).
There's no good solution to the connecting-dialog imho:
The best I could achieve is a solution where it would reconnect automatically after 30s, the dialog stayed opened (see Commit 2, eclipse-che/che#23587 (comment)). Given that this isn't a good solution and the approach to achieve it is repeatedly querying of remote-dev-server status (via pod-exec), I thought of dropping it, leaving the issue as KNOWN ISSUE. Leaving the small fix of Commit 1 which is this PR here.
I'll post a comment to the jetbrains forum and hope that they fix the issue on their side.
Agree?