we should automate board identification on blueos

I don't think we _need_ to add support to board one by one. all information we need to automate this should be present in the [hwdef files in ardupilot.](https://github.com/ArduPilot/ardupilot/tree/master/libraries/AP_HAL_ChibiOS/hwdef) parsing then might be annoying, though.

we could also do as is done in the uploader script, maybe:
```python
# default list of port names to look for autopilots
default_ports = ['/dev/serial/by-id/usb-Ardu*',
'/dev/serial/by-id/usb-3D*',
'/dev/serial/by-id/usb-APM*',
'/dev/serial/by-id/usb-Radio*',
'/dev/serial/by-id/usb-*_3DR_*',
'/dev/serial/by-id/usb-Hex_Technology_Limited*',
'/dev/serial/by-id/usb-Hex_ProfiCNC*',
'/dev/serial/by-id/usb-Holybro*',
'/dev/serial/by-id/usb-mRo*',
'/dev/serial/by-id/usb-modalFC*',
'/dev/serial/by-id/usb-Auterion*',
'/dev/serial/by-id/usb-*-BL_*',
'/dev/serial/by-id/usb-*_BL_*',
'/dev/serial/by-id/usb-Swift-Flyer*',
'/dev/serial/by-id/usb-CubePilot*',
'/dev/serial/by-id/usb-Qiotek*',
'/dev/tty.usbmodem*']
```

Start by reviewing the linked ArduPilot hwdef files and the existing uploader script, since no BlueOS file or entry point is named. Determine how board information and port patterns can be derived, then define completion as automatic board identification without adding each board individually.

Written by the indexing model from the issue text.