Move test control logic to Haskell

[martijnbastiaan]

This PR moves test control from TCL to Haskell. Moving this to Haskell makes sure that we can easily control the individual steps (programming, test control) and interleave it with other steps, such as starting GDB servers, and monitoring UART output. We mostly do this to make sure we can move to a software based development loop.

TODO

• Write wrapper to control Vivado from Haskell (@martijnbastiaan)
  • Introduce VivadoM for ease of usage (@martijnbastiaan)?
• Rewrite existing logic in Shake / HardwareTest.tcl (@JvWesterveld)
  • Fix failing HITL tests (rebasing first might help)
  • Fix clock control report generation in bittide-tools/clockcontrol/plot/Main.hs, which is broken for the new HITL test definition types (initial attempt in f35d240)
• Rebase on staging branch (see Add fourmolu #595)
• Wait for https://github.com/bittide/bittide-hardware/actions/runs/10743081981
• Wait for https://github.com/bittide/bittide-hardware/actions/runs/10792200155

Future work

• Cleanup VIO and ILA probe detection and usage code in bittide-shake/src/Clash/Shake/Vivado.hs
• Perhaps let execPrint from vivado-hs print Vivado output to stdout directly instead of only when the relevant Tcl code has finished executing
• Perhaps remove most functions in vivado-hs/src/Vivado/Tcl.hs and instead use execPrint or execCmd directly
• Perhaps replace System.Clock with Data.Time(.Clock) and Data.Time.Format in bittide-shake/src/Clash/Shake/Vivado.hs to print fancier formatted test durations

[martijnbastiaan]

Overall this LGTM, great work @JvWesterveld!

I'm only missing some documentation in a couple of places, and I think Iter is a misnomer.

[JvWesterveld]

Latest changes LGTM. I have a few more mostly minor comments, partially concerning my own code.