Transport device disconnected

[mroz22]

• 1st commit - narrow error cases from all node-usb and web-usb and convert them to "device disconnected during action" in the same way legacy bridge does. This helps with proper error handling on the trezor-connect layer.
• 2nd commit - do not release disconnected devices.
  • Trying to do this causes node bridge - another case of segfault 11 #15336 on my machine (mac-arm). I am unaware of anyone else who could reproduce it locally.
  • The legacy bridge is okay with it, and I haven't found out yet what the key difference is. But anyway, it doesn't feel right to me to release devices that are no longer present. The only possible problem this may cause could be when we false positively handle an error as a disconnected device and omit proper clean up.
  • Here is a little table where I tested the scenario explained in node bridge - another case of segfault 11 #15336 and it worked for me locally.

fixes #15336	legacy bridge	node bridge	webusb
enable labelling - button request - disconnect
get address - button request disconnect

• 3rd commit - split the 'unacquired screen' into two 1] unacquired 2] device-used-elsewhere
  • now there is a common "unacquired" screen. Unacquired here means that features of the device are not known because some bug happened. There is a "Try again" button.
  • then there is a special case of "used-elsewhere" screen that appears if we know device.transportSessionOwner.
  • todo: maybe it could be shown also when device.used = true? This way this screen never renders for the legacy bridge since it never returns transportSessionOwner.
• 4th commit - rework device.run error handling
  • in general, there are the following categories of errors:
    • recoverable -> show try again button
    • non-recoverable -> don't show button. only maybe reloading or reconnect could help
    • device disconnected -> do nothing. todo: maybe we should enumerate in this case to be sure that it really disconnected?
• 5th commit - thanks to previous changes, unreadable device state is now better targeted and we don't need to show that many troubleshooting tips anymore.
  • unreadable non-hid device. this is not recoverable. This is typically the case of missing synchronization between apps for whatever reason.
  • 
  • webusb + unreadable hid device
  • 
  • unreadable hid device + suite desktop - allows to toggle legacy bridge
  • 

related issues:

• node bridge - another case of segfault 11 #15336
• Device undiscoverable after Suite update #15676
• Suite reports no connected device after Suite update #15480

[github-actions]

🚀 Expo preview is ready!

• Project → trezor-suite-preview
• Platforms → android, ios
• Scheme → trezorsuitelite
• Runtime Version → 12
• More info

Learn more about 𝝠 Expo Github Action