[platform-debug-dev] Extensible Launch Modes

["Darin Wright" <Darin_Wright@xxxxxxxxxx>]

The debug platform now supports extensible launch modes. The debug platform contributes three modes - run, debug, and (now) profile. The support has been released to HEAD and will be in the first 3.0 milestone build, the week of June 6th.

Summary:
* Clients may contribute a launch mode to the debug platform via the "launchModes" extension point. The debug platform already contributes "run", "debug", and "profile"
* Clients may contribute a launch delegate for a specific launch configuration type and launch mode via the "launchDelegates" extension point. In the past, a contributor of a launch configuration was the only party allowed to contribute a launch delegate. The new support allows others to re-use existing launch configurations in a different launch mode by plugging in a launch delegate for that mode. For example, a client could contribute a launch delegate to launch a Java application in "profile" mode.
* Clients may contribute a launch tab group for a specific launch configuration type and mode. This allows clients to contribute their own/extra UI that may be required for a new launch mode. This means that a different set of tabs may appear in the launch dialog, for a config type, depending on the launch mode. Generally, clients contributing a launch delegate will also contribute a tab group for that mode.
* The "launchConfigurationTabGroup" extension point has been enhanced to allow clients to specify a default perspective associated with a launch mode. This defines the default perspective that is  opened/switched to when a configuration is launched (in the associated mode). For example, a client contributing a profiler for Java Applications, may have their own perspective that should be displayed when a Java Application is profiled.

Notes:
* The "profile" actions have been temporarily defined in their own action set. Since the SDK does not ship a profiler, the profile actions are always disabled. Rather than display disabled actions, the profile actions are now in their own action set that a user can turn on, as required.
* Perspective switching is now controlled via the launch dialog, by selecting a launch configuration type - for example, Java Application. When a type is selected, the perspective settings are displayed. The settings effect all configurations of an associated type (per launch mode).

Darin