Config.launch now supports defining `launch_cls` entry_points per alias

[MHendricks]

If launching houdini using hab-gui using habw.exe gui launch, houdini would not be able to print. The stdout/stderror objects will not accept write's.

This seems to be happening because Launcher uses subprocess.PIPE to capture stdout/stderr. Switching to the normal subprocess.Popen class instead fixes houdini.

Checklist

• [x] I have read the CONTRIBUTING.md document
• [x] I formatted my changes with black
• [x] I linted my changes with flake8
• [x] I have added documentation regarding my changes where necessary
• [x] Any pre-existing tests continue to pass
• [x] Additional tests were made covering my changes

Types of Changes

• [x] Bugfix (change that fixes an issue)
• [x] New Feature (change that adds functionality)
• [ ] Documentation Update (if none of the other choices apply)

Proposed Changes

This PR makes it so we can define a per-alias launcher class.

Example .hab.json for houdini:

{
    "name": "houdini19.5",
    "aliases": {
        "windows": [
            [
                "houdinicore", {
                    "cmd": "C:\\Program Files\\Side Effects Software\\Houdini 19.5.716\\bin\\houdinicore.exe",
                    "icon": "{relative_root}/.img/houdini.ico",
                    "label": "Houdini Core",
                    // Launcher captures stdout/error and this breaks printing
                    // when launching houdini's gui. Just use the standard class
                    "launch_cls": {"subprocess": "subprocess:Popen"},
                }
            ]
        ]
    }
}