Good testing tracking issue (allegedly)

[atalii]

• testing script for rendering specifically (thank you @ulahello !)
• CI that continuously builds (CI #22)
• CI that continuously tests
• CI that runs in a tolerable amount of time (cachix and/or self-hosted runner)
• test backend that dumps the framebuffer to a file (see Test backend #35)
• test harness that uses the aforementioned backend to test threads and command code intertwined with rendering
• unit testing on the web server
• integration testing with the web server and everything else
• building an image for the rpi that this ought to run on, which can be tested manually in qemu
• ...maybe adding automated tests to that image?
• simulate OOMs and other possibly sporadic error conditions