Bundle mission-control into Triple-C instead of cloning from GitHub

The mission-control (Flight Control) project is being closed upstream.
This embeds the project files directly in the repo under container/mission-control/,
bakes them into the Docker image at /opt/mission-control, and copies them into place
at container startup instead of git cloning from GitHub.

Also adds missing osc52-clipboard, audio-shim, and triple-c-sso-refresh to the
programmatic Docker build context in image.rs.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

app/src-tauri/src/docker/container.rs

@@ -80,7 +80,7 @@ When working on any project that has a `.flightops/` directory, follow the Fligh
 
 const MISSION_CONTROL_PROJECT_INSTRUCTIONS: &str = r#"## Flight Operations
 
-This project uses [Flight Control](https://github.com/msieurthenardier/mission-control) for structured development.
+This project uses **Flight Control** (bundled with Triple-C) for structured development.
 
 **Before any mission/flight/leg work, read these files in order:**
 1. `.flightops/README.md` — What the flightops directory contains