Better inform of debug session errors to the user

[arturocuya]

Currently the debug session logs show messages like this when there's an error connecting to a device:

DebugServer: Invalid response code: 577

In this case, the problem is known: The device requires a system update before sideloading apps. The logs could show a more human readable message, like this:

DebugServer: Error (577) - Your device requires a system update before accepting connections. Follow these instructions to manually check for updates https://support.roku.com/article/208755668.

We should do this for all known error codes.

[timbyu]

I was getting a 577 but had no idea how to fix it. Rebooting my Roku did not resolve the problem. I verified a couple of times that the software on my device is up to date. I found restarting VS Code would allow the debugger to work again for a time. By the next day I was seeing the 577 error again. Any information that would help me figure out what is going wrong would be welcomed.

I just found if I run "Developer: Restart Extension Host" from the command pallet it starts working again.

[chrisdp]

This is a safe guard in the Roku OS where the device wants to "phone home" every so often. If it can't do so the side-loading commands will respond with a 577 response code.

The fix is simply checking for updates on the device in settings. We are currently working on detecting this case and displaying a more informative error.