Drop Apollo's enabled:false trigger instruction

[elias-ba]

As an AI-assistant user, I want workflows the assistant generates to arrive as drafts through Lightning's lifecycle, so that newly created workflows are never live by accident and the lifecycle stays a single Lightning concern.

Part of #4852 (Sandbox DevX epic).

What's broken

Apollo (the AI assistant service) emits workflow YAML with triggers defaulted to enabled: false. Now that trigger-enabled is owned by the workflow lifecycle (Go live / Switch to draft) and is derived from state rather than set directly, that instruction emits a field Lightning ignores on the lifecycle path.

How it surfaced

Found during the lifecycle epic while mapping how the AI apply path interacts with the new state field. Apollo is stateless and has no lifecycle concept, which is correct and should stay that way. The only stale piece is the explicit enabled: false trigger instruction.

What to fix

In the apollo repo, remove the enabled: false trigger instruction from gen_project_prompts.yaml. AI-generated workflows should arrive as drafts via Lightning's lifecycle default, not by Apollo setting trigger flags. Lifecycle stays a Lightning concern; Apollo stays stateless.

Note: Apollo's existing read_only input flag (about IDs and code preservation) is unrelated to the lifecycle read-only lock and should not be touched.

Acceptance criteria

• Given an AI-generated workflow, when it is applied in Lightning, then it lands as a draft via the lifecycle default (no explicit trigger-enabled instruction from Apollo).
• Apollo's unrelated read_only input flag is left untouched.

Dependencies

Cross-repo (apollo). Phase M1 (lifecycle spine). Small, standalone cleanup.