Clarify SSH extension timeout copy

[alokedesai]

Description

Update SSH remote server timeout copy so timeout failures lead with "Timed out" and clarify that the user's SSH session can continue while advanced features are unavailable.

Linked Issue

• The linked issue is labeled ready-to-spec or ready-to-implement.
• Where appropriate, screenshots or a short video of the implementation are included below (especially for user-visible or UI changes).

Testing

• cargo test -p remote_server transport::tests:: -- --nocapture

• cargo test -p remote_server

• cargo clippy -p remote_server --all-targets -- -D warnings

• Manually demoed the real banner by connecting Warp to a local SSH server whose SSH rc sleeps longer than the extension check timeout.

• I have manually tested my changes locally with ./script/run

Screenshots / Videos

ssh_extension_timeout_banner_demo.mp4
SSH extension timeout banner

Agent Mode

• Warp Agent Mode - This PR was created via Warp's AI Agent Mode

CHANGELOG-BUG-FIX: Clarified that SSH extension setup timeout errors are timeouts and do not stop the SSH session.

_{To show artifacts inline, enable in settings.}

  

[cla-bot]

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have the users @cursoragent on file. In order for us to review and merge your code, each contributor must visit https://cla.warp.dev to read and agree to our CLA. Once you have done so, please comment @cla-bot check to trigger another check.

[cla-bot]

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have the users @cursoragent on file. In order for us to review and merge your code, each contributor must visit https://cla.warp.dev to read and agree to our CLA. Once you have done so, please comment @cla-bot check to trigger another check.