Support for Defining an `asconfig.json` Base

MASCOT now allows you to specify a base (or "blueprint") for all generated *.asconfig.json files.

This allows you to include persistent settings in-there, such as AIR packaging options (e.g., airOptions) or specialized compiler flags (e.g., advanced-telemetry). This kind of settings would be overwritten if you were to add them directly into each generated *.asconfig.json file, not to mention all the effort.

Please refer to the Asconfig Base section in the documentation for more details.

Known limitations in v.1.0.5

• No parallel compilation available. While Visual Studio Code's build tasks system does permit unrelated tasks to run in parallel, MASCOT does not leverage this, and always generates build tasks that are executed sequentially, even if they are unrelated. This also wastes time.
• The src, bin and lib folder names are assumed by MASCOT and cannot be changed. If an ActionScript project uses, e.g., projsrc for its source folder name, that will not be recognized by MASCOT as a valid project, and will be ignored.
• MASCOT does not currently recognizes couplings defined in MXML classes via custom MXML tags (by contrast, couplings defined in fx:Script sections are accounted for).
• MASCOT cannot detect couplings to classes that live in the global package, or live in another project but in the same package as the current class. The g_manual_dependencies argument/configuration directive can be used as a workaround, to manually couple such classes.