## Why
Meeting Assistant currently has one global configuration, one hotkey, and one implicit ASR/runtime setup. In practice, the user needs to start meetings with different speech-recognition settings, such as German-only versus English-only recognition, without editing configuration and restarting between meetings.

## What Changes
- Add named launch profiles to configuration.
- Treat the root `MeetingAssistant` configuration as the `default` launch profile.
- Resolve non-default launch profiles by copying the default settings and binding the named profile override onto that copy.
- Add profile-aware endpoint routes while preserving the existing default-profile URLs.
- Register one global hotkey per launch profile, requiring distinct hotkey definitions.
- Add an `english` launch profile that keeps the current default settings except for English Azure Speech recognition and its own hotkey.

## Impact
- Existing URLs and the existing hotkey continue to operate the default profile.
- Named profiles are addressed through profile URLs, allowing diagnostics and recording commands to select the desired backend/language profile.
- Speech pipeline creation becomes profile-aware.