Retire the daemon_auto_start feature flag (#58940)

## What changed

Eligible interactive launches now start or reuse the shared daemon regardless of `features.daemon_auto_start`. Remote-control daemon eligibility also no longer checks this flag. Use `--no-daemon` to run without the shared background server.

Treat `daemon_auto_start` as removed: ignore configured values with a migration notice, ignore managed requirements with a warning, and hide the flag from experimental feature discovery. Remove its launch telemetry tag.

## Testing

Extend retired-feature requirement coverage and add a migration-notice snapshot. Update CLI and TUI integration tests for daemon startup and explicit `--no-daemon` usage.

GitOrigin-RevId: e0290e5acd4bc0169a0f71c3296c567e46269ce3

codex-rs/cli/src/remote_control_cmd.rs

@@ -16,7 +16,6 @@ use codex_app_server_protocol::RemoteControlPairingStartResponse;
 use codex_arg0::Arg0DispatchPaths;
 use codex_config::LoaderOverrides;
 use codex_core::config::ConfigBuilder;
-use codex_features::Feature;
 use codex_protocol::protocol::SessionSource;
 use codex_utils_absolute_path::AbsolutePathBuf;
 use codex_utils_cli::CliConfigOverrides;
@@ -161,8 +160,7 @@ async fn daemon_eligible(root_config_overrides: &CliConfigOverrides) -> anyhow::
     let Ok(config) = ConfigBuilder::default().build().await else {
         return Ok(false);
     };
-    Ok(config.features.enabled(Feature::DaemonAutoStart)
-        && !codex_tui::uses_wsl_drvfs(&config.codex_home))
+    Ok(!codex_tui::uses_wsl_drvfs(&config.codex_home))
 }
 
 fn print_remote_control_progress(json: bool, message: &str) -> anyhow::Result<()> {