Include tests listed by Christoph Sprenger

[Rangi42]

https://github.com/c-sp/game-boy-test-roms lists many test ROMs that we don't yet run:

• AGE tests: https://github.com/c-sp/age-test-roms
• Scribbltests: https://github.com/Ashiepaws/scribbltests (another of Ashiepaws' test ROMs)
• Gambatte test suite: https://github.com/pokemon-speedrunning/gambatte-core/tree/master/test
• GBMicrotest collection: https://github.com/aappleby/GBMicrotest
• MBC3 Bank Tester: https://github.com/EricKirschenmann/MBC3-Tester-gb
• little-things-gb tests: https://github.com/pinobatch/little-things-gb
• TurtleTests: https://github.com/Powerlated/TurtleTests

It also lists the Wilbert Pol tests, but #28 covers that.

[pinobatch]

These tests from little things might be viable in a shootout:

• redfromoam
• sgbears 🐻️ and trnstress 🐻️ are interactive but could probably be decomposed into several ROMs, each automatically choosing one value

As for these, I'm failing to imagine how to make them relevant; change my mind.

• afterglow, bordercrossing, drumkit 🥁️, sgbkeyirq, and tellinglys 🤥️ are interactive
• bdos, ca83, gbpng 🧜‍♀️️, nosuchthing, and simplest demonstrate build tools and programming techniques, not particularly testing hardware behavior
• tearing lacks an end state
• uaflag is too easy

[Rangi42]

IMO it's fine if we try to be comprehensive, even if some tests are "too easy". If this shootout becomes the main reference for GB tests, it's how community members would even learn which tests are easy or hard, rather than word of mouth. But yeah, some tests just won't be feasible for us. Thanks for listing the viable ones. (c-sp's repo includes "parts of" little-things-gb: firstwhite and tellinglys.)