New 'auto mode environment' setting carried through bridge/cloud sessions

What

• A new optional auto_mode_environment field was added: a config schema field, a matching autoModeEnvironment: [] default in session state, and support for it in the bridge/cloud session-launch path.
• Sessions launched via the bridge/cloud path can receive an auto_mode_environment array of strings from the dispatching service; each entry is validated (length caps, no control/invisible characters) and injected into the session's context as "Stated by the service that dispatched this session ..." lines.
• When spawning a CLI session, Claude Code now also computes autoModeSettingsJson from any configured autoModeEnvironment list and includes it in the launch config alongside mcpConfig/appendSystemPrompt.
• When spawning a worker for a remote-control (bridge) session whose work item carries auto_mode_environment, Claude Code re-checks the local userSettings/policySettings auto-mode environment config and passes a computed userAutoModeEnvironmentConfigured flag into the session-spawn call.
• New telemetry was added: bridge server-config apply/rejected events now include an auto_mode_environment count and a carried_auto_mode_environment flag, plus a new debug reason, auto_mode_environment_dropped, that fires when the value was carried but ended up empty after filtering.

Why This lets a service that dispatches automated ("auto mode") sessions describe the environment it's running in, so that description can be surfaced to the model as context and tracked through config and telemetry.