ViddikShowroomLauncher

Opens ViddikShowroom over whatever registry the KSP processor generated in the module this runs against — the browser half of viddik, without every consumer hand-writing the same fun main().

The registry is loaded reflectively on purpose: it is generated into the consumer's test source set, so this module can't see the class at compile time, only on the runtime classpath the viddikShowroom Gradle task assembles.