a previous commit removed logger_backend_sqlite. This was a valuable tool for getting the reason for a start failure.

Adding ramoops_logger will be able to accomplish the same thing with pretty much no overhead

Currently we have things like:

assert get_border_command() == [send_command: {60, 51}]

While the command being sent is provided in hex:

write_command(state, 0x3C, border_data)

0x3C is output as 60 and that's why things are this way right now. We should probably change it so that the connection remains clear.