Hardcoding /dev/ttyACM{0,1} doesn't work when ports don't
enumerate exactly as that.

The programmer already seems to enumerate nicely inside
`/dev/serial/by-id/*-if{00,02,04}` for control, ec and ap respectively.
Why don't we semantically use those?

BUG=None
TEST=I can use the programmer on lotus without unplugging my led panels (since they always enumerate first)
TEST=./flash_azalea_ec.sh ~/framework/cros/src/platform/ec/build/zephyr/marigold/output
TEST=DEVICE="/dev/serial/by-id/usb-Framework_CMSIS-1" ./flash_azalea_ec.sh ~/framework/cros/src/platform/ec/build/zephyr/marigold/output
TEST=DEVICE="/dev/serial/by-id/usb-Framework_CMSIS-2" ./flash_azalea_ec.sh ~/framework/cros/src/platform/ec/build/zephyr/marigold/output

Signed-off-by: Daniel Schaefer <dhs@frame.work>

Signed-off-by: Daniel Schaefer <dhs@frame.work>

Flash Nuvoton using minimal UART adapter setup

Let's move all the old teensy stuff into a folder as we're preparing to
include a bunch more information in here that might be lost in between
the platformio stuff.

BUG=New framework debugger!
TEST=.github stuff still works
TEST=all files are still here
TEST=common stuff (eg: scripts) that's still relevant is still in the same spot.

Signed-off-by: Daniel Schaefer <dhs@frame.work>

Signed-off-by: Daniel Schaefer <dhs@frame.work>

Patching fails:
2 out of 2 hunks FAILED -- saving rejects to file packages/framework-arduinoteensy/cores/teensy4/yield.cpp.rej

Firmware never worked, only Teensy 3.

Signed-off-by: Daniel Schaefer <dhs@frame.work>

Added a bunch of documentation about the various debugging interfaces on
the framework computers.

BUG=We want to publicize this at the same time as the debug tool.
TEST=Buy parts from digikey, follow the instructions, have them work

This contains information on how to use the CPU and EC UART consoles.

This also contains the information that we'll link to from the
https://fr.mw/FRANNJ00TP shortlink.

TEST=Follow instructions