Allow modules and module groups to be excluded from debug output

[serin-delaunay]

Debug tileset output requires a lot of graphics textures simultaneously (one per module per corner), and some graphics cards don't have enough memory for that, which leads to crashes. These crashes could be avoided by allowing users to make debug tilesets for only a subset of the component modules.

I see three ways to do this:

1. Add fields to the module group JSON schema, specifying which modules should generate debug tilesets. This could be default-on or default-off with a list of exceptions:

{
  "defaultoutputmodule":"OUTPUT",
  "DefaultDebugTilesetGeneration":"true",
  "IncludeDebugTilesets":["OUTPUT"],
  "ExcludeDebugTilesets":["null"],
  "modules":{
    "OUTPUT":{
      "type":"TranslatePoint",
      "Translation":[1.1,2.2,3.3],
      "SourceModule":["null"]
    },
    "null":{
      "type":"Const",
      "ConstValue":0
    }
}

2. Add a field to all module schemas, specifying whether the module should generate a debug tileset. This would be more robust when changing names in a module group, but may also reduce compatibility with RESTnoise. Modules are already decoded twice (once for source module names by NoiseSourcesCodec, once for individual attributes); this system could be extended to indicate debug modules.

{
  "defaultoutputmodule":"OUTPUT",
  "modules":{
    "OUTPUT":{
      "type":"TranslatePoint",
      "Translation":[1.1,2.2,3.3],
      "SourceModule":["null"],
      "DebugTileset":true
    },
    "null":{
      "type":"Const",
      "ConstValue":0,
      "DebugTileset":false
    }
}

3. Specify debug modules through the interface. I think this would be far too laborious for the command line interface, but it could be done through a GUI. However, the GUI should probably do this just by editing the options.

I favour option 2.