feat: config field in /cypher/execute — node-level component override

- /cypher/execute now accepts separate `config` field:
  {node_name: {component: "cmp_19e62efd", ...staticParams}}
- graph-builder reads config[node].component to override componentId
  (supports cmp_ hash, rec_ hash, or canonical_id)
- config[node] other fields become node.data (static params merged at runtime)
- acr run now sends workflow.config as separate `config` (not flattened into context)
- context is now only --input dynamic params

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

cypher-executor/src/actions/cypher-handlers.ts

@@ -32,6 +32,7 @@ export async function handleCypherExecute(
   context: Record<string, unknown> | undefined,
   graphId: string,
   graphName: string,
+  config: Record<string, Record<string, unknown>> | undefined,
   env: Bindings,
   waitUntil: (promise: Promise<void>) => void,
 ): Promise<{ success: boolean; data?: unknown; error?: string; trace?: unknown; duration_ms: number; graph?: ExecutionGraph }> {
@@ -49,7 +50,7 @@ export async function handleCypherExecute(
     );
   }
 
-  const graph = buildExecutionGraph(parsed, nodeResults, graphId, graphName);
+  const graph = buildExecutionGraph(parsed, nodeResults, graphId, graphName, config);
   const parseResult = graphSchema.safeParse(graph);
   if (!parseResult.success) {
     throw new Error('圖定義產生失敗');