Add --skip-managed-config and decouple managed config from --skip-pre…

[AarushiShah-db]

…flight

--skip-managed-config (on ucode configure and every launcher) ignores the workspace's managed coding-agent config for that run, behaving as though ENABLE_MANAGED_AGENT_CONFIG were unset — it clears the env var for the process, so the single managed_agent_config_enabled() gate short-circuits every managed path (fetch/apply, budget read, MCP registration, the configure reject flow, and the bare-ucode agent picker). Per-invocation only.

--skip-preflight no longer touches managed config: it now means only "skip the per-launch auth + AI Gateway re-validation." Dropped its cache-instead-of-refresh branch, its budget-read and MCP-registration gating, and the bare-ucode "no config to pick an agent" error.

Co-authored-by: Isaac

[lilly-luo]

i don't understand why we need this - doesn't this undercut the purpose of the managed config by giving userse a way around it?

[AarushiShah-db]

don't understand why we need this - doesn't this undercut the purpose of the managed config by giving userse a way around it?
@lilly-luo we need a way to disable the feature for omniagent. omniagent requires ucode configure to be a non-interactive command, but once we roll this feature out 'ucode configure' will start to ask admins to run "ucode setup" instead (with an interactive prompt of yes or no)

[lilly-luo]

@lilly-luo we need a way to disable the feature for omniagent. omniagent requires ucode configure to be a non-interactive command, but once we roll this feature out 'ucode configure' will start to ask admins to run "ucode setup" instead (with an interactive prompt of yes or no)

i see. can we hide this command from the --help section then? ideally a normal ucode user never knows about it.

[AarushiShah-db]

@lilly-luo updated so it doesnt show up in --help