Have the TUI try to find the board's serial path automatically

[rrbutani]

what

^

We want to support: WSL, Windows, macOS, and Linux.

Here's some prior art from a few years ago.

steps

...

where

branch: feat-...

open questions

baud rate detection, etc. is tricky; also knowing what device types to look for becomes device specific again

I'm thinking that we have device crates (i.e. utp-tm4c) provide a host counterpart (i.e. utp-tm4c-device-info) that provides:

• baud rate
• device short name (i.e. tm4c)
• URL/repo for binaries for the board (for later)
• the pinout (documentation; it'd be neat to show this in the TUI too though...)
• host-only functions that, when run, try to find the device of the given type

(we should also eventually make a template utp device repo, etc.)

We can then go have a tui-devices crate that pulls in all of these, etc.
And have the tui support --device <short name> in addition to the --device board=<path>:baud_rate.