Refactor workflow-logic-function-interaction (#17699)

# Refactor workflow–logic function interaction

## Why

Workflow code steps and standalone logic functions shared the same build
layer and DB layer, which blurred two use cases: code steps belong to a
workflow version; standalone functions are deployable units. That made
workflow code steps harder to own and evolve.

## Goal

Treat code steps as **workflow-owned**: build and run them in workflow
context, and expose workflow-scoped APIs so the editor can load, test,
and save code step source without going through the generic
logic-function layer.

packages/twenty-front/src/modules/logic-functions/graphql/mutations/executeOneLogicFunction.ts

@@ -0,0 +1,13 @@
+import { gql } from '@apollo/client';
+
+export const EXECUTE_ONE_LOGIC_FUNCTION = gql`
+  mutation ExecuteOneLogicFunction($input: ExecuteOneLogicFunctionInput!) {
+    executeOneLogicFunction(input: $input) {
+      data
+      logs
+      duration
+      status
+      error
+    }
+  }
+`;

packages/twenty-front/src/modules/logic-functions/graphql/mutations/updateLogicFunctionSource.ts

@@ -0,0 +1,7 @@
+import { gql } from '@apollo/client';
+
+export const UPDATE_LOGIC_FUNCTION_SOURCE = gql`
+  mutation UpdateLogicFunctionSource($input: UpdateLogicFunctionSourceInput!) {
+    updateLogicFunctionSource(input: $input)
+  }
+`;

packages/twenty-front/src/modules/logic-functions/graphql/queries/getLogicFunctionSourceCode.ts

@@ -0,0 +1,7 @@
+import { gql } from '@apollo/client';
+
+export const GET_LOGIC_FUNCTION_SOURCE_CODE = gql`
+  query GetLogicFunctionSourceCode($input: GetLogicFunctionSourceCodeInput!) {
+    getLogicFunctionSourceCode(input: $input)
+  }
+`;