Improve Handling of frp Errors and Prevent Daytona from Crashing

[nkkko]

Describe the bug When frp (Fast Reverse Proxy) throws an error, potentially due to slow networking or other issues, Daytona crashes. The HTML error output from frp is not properly parsed and displayed, resulting in a poorly formatted, hard-to-read error message.

To Reproduce Steps to reproduce the behavior:

1. Set up an environment using Daytona that relies on frp for networking.
2. Introduce a networking issue to trigger an error from frp.
3. Observe that Daytona crashes and the frp error message is displayed in an unformatted HTML.

Expected behavior Daytona should handle frp errors more gracefully:

• Capture and log the error without crashing.
• Properly parse and display HTML error messages in a readable format.

Screenshots

Desktop (please complete the following information):

• OS: macos sonoma
• Daytona Version: v0.21.0

[RS-labhub]

This is harder to reproduce, any other way to reproduce this?

[Tpuljak]

Split part of this issue into https://github.com/daytonaio/daytona/issues/953.

This issue will focus on handling FRP errors more clearly.