Launching/Bootstrapping Refactoring

The code which creates the PotomacInitializer and bootstraps all Potomac applications has been rewritten to allow users to launch Potomac with alternative logic. The standard logic starts the specified template but a common need is to bootstrap a Potomac and then run unit tests without loading the template. The bootstrapping classes in potomac_core have also been promoted to public (i.e. they’re now supported classes). These include Launcher, LauncherManifest, and LaunchRunner. Users who wish to launch a Potomac app from a custom application project (i.e. one that does not include the Potomac application nature and does not use the standard PotomacInitializer.as) will need to set the potomac_core as an RSL and then call Launcher#launch providing a LauncherManifest and a LaunchRunner.

Other changes

The example projects in the 06/12 build were distributed with incorrect bundle paths. This build resolves that issue.

The long standing issue that occurs when cleaning multiple projects in the workspace has been fixed. The problem manifested itself in errors referencing the Flex code model.