feat: Add agent role assignment and database CRUD tools for AI agent nodes (#12888)

This PR introduces a significant enhancement to the role-based
permission system by extending it to support AI agents, enabling them to
perform database operations based on assigned permissions.

## Key Changes

### 1. Database Schema Migration
- **Table Rename**: `userWorkspaceRole` → `roleTargets` to better
reflect its expanded purpose
- **New Column**: Added `agentId` (UUID, nullable) to support AI agent
role assignments
- **Constraint Updates**: 
- Made `userWorkspaceId` nullable to accommodate agent-only role
assignments
- Added check constraint `CHK_role_targets_either_agent_or_user`
ensuring either `agentId` OR `userWorkspaceId` is set (not both)

### 2. Entity & Service Layer Updates
- **RoleTargetsEntity**: Updated with new `agentId` field and constraint
validation
- **AgentRoleService**: New service for managing agent role assignments
with validation
- **AgentService**: Enhanced to include role information when retrieving
agents
- **RoleResolver**: Added GraphQL mutations for `assignRoleToAgent` and
`removeRoleFromAgent`

### 3. AI Agent CRUD Operations
- **Permission-Based Tool Generation**: AI agents now receive database
tools based on their assigned role permissions
- **Dynamic Tool Creation**: The `AgentToolService` generates CRUD tools
(`create_*`, `find_*`, `update_*`, `soft_delete_*`, `destroy_*`) for
each object based on role permissions
- **Granular Permissions**: Supports both global role permissions
(`canReadAllObjectRecords`) and object-specific permissions
(`canReadObjectRecords`)

### 4. Frontend Integration
- **Role Assignment UI**: Added hooks and components for
assigning/removing roles from agents

## Demo


https://github.com/user-attachments/assets/41732267-742e-416c-b423-b687c2614c82

---------

Co-authored-by: Antoine Moreaux <moreaux.antoine@gmail.com>
Co-authored-by: Lucas Bordeau <bordeau.lucas@gmail.com>
Co-authored-by: Charles Bochet <charles@twenty.com>
Co-authored-by: Guillim <guillim@users.noreply.github.com>
Co-authored-by: Charles Bochet <charlesBochet@users.noreply.github.com>
Co-authored-by: Weiko <corentin@twenty.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions <github-actions@twenty.com>
Co-authored-by: Félix Malfait <felix.malfait@gmail.com>
Co-authored-by: Marie <51697796+ijreilly@users.noreply.github.com>
Co-authored-by: martmull <martmull@hotmail.fr>
Co-authored-by: Thomas Trompette <thomas.trompette@sfr.fr>
Co-authored-by: Etienne <45695613+etiennejouan@users.noreply.github.com>
Co-authored-by: Baptiste Devessier <baptiste@devessier.fr>
Co-authored-by: nitin <142569587+ehconitin@users.noreply.github.com>
Co-authored-by: Paul Rastoin <45004772+prastoin@users.noreply.github.com>
Co-authored-by: prastoin <paul@twenty.com>
Co-authored-by: Vicky Wang <157669812+vickywxng@users.noreply.github.com>
Co-authored-by: Vicky Wang <vw92@cornell.edu>
Co-authored-by: Raphaël Bosi <71827178+bosiraphael@users.noreply.github.com>

packages/twenty-server/src/engine/metadata-modules/agent/constants/agent-config.const.ts

@@ -0,0 +1,3 @@
+export const AGENT_CONFIG = {
+  MAX_STEPS: 10,
+};

packages/twenty-server/src/engine/metadata-modules/agent/constants/agent-system-prompts.const.ts

@@ -0,0 +1,71 @@
+export const AGENT_SYSTEM_PROMPTS = {
+  AGENT_EXECUTION: `You are an AI agent node in a workflow builder system with access to comprehensive database operations. Your role is to process inputs, execute actions using available tools, and provide structured outputs that can be used by subsequent workflow nodes.
+
+AVAILABLE DATABASE OPERATIONS:
+You have access to full CRUD operations for all standard objects in the system:
+- CREATE: create_[object] - Create new records (e.g., create_person, create_company, create_opportunity)
+- READ: find_[object] and find_one_[object] - Search and retrieve records
+- UPDATE: update_[object] - Modify existing records
+- DELETE: soft_delete_[object] and destroy_[object] - Remove records (soft or permanent)
+
+Common objects include: person, company, opportunity, task, note etc. and any custom objects.
+
+CRITICAL PERMISSION CHECK:
+Before attempting any operation, you MUST first check if you have the required tools available. If you do NOT have the necessary tools to perform the requested operation, you MUST immediately respond with:
+"I cannot perform this operation because I don't have the necessary permissions. Please check that I have been assigned the appropriate role for this workspace."
+
+DO NOT describe what you would do, DO NOT list steps, DO NOT simulate the operation. Simply state that you cannot perform the action due to missing permissions.
+
+Your responsibilities:
+1. FIRST check if you have the required tools for the requested operation
+2. If tools are NOT available, immediately state you lack permissions - do not proceed further
+3. If tools ARE available, analyze the input context and prompt carefully
+4. Use available database tools when the request involves data operations
+5. For any request to create, read, update, or delete records, use the appropriate tools
+6. If no database operations are needed, process the request directly with your analysis
+
+Workflow context:
+ - You are part of a larger workflow system where your output may be used by other nodes
+ - Maintain consistency and reliability in your responses
+ - Consider the broader workflow context when making decisions
+ - If you encounter data or perform actions, document them clearly in your response
+
+Tool usage guidelines:
+ - ALWAYS use tools for database operations - do not simulate or describe them
+ - Use create_[object] tools when asked to create new records
+ - Use find_[object] tools when asked to search or retrieve records
+ - Use update_[object] tools when asked to modify existing records
+ - Use soft_delete_[object] or destroy_[object] when asked to remove records
+ - Always verify tool results and handle errors appropriately
+ - Provide context about what tools you used and why
+ - If a tool fails, explain the issue and suggest alternatives
+
+CRITICAL: When users ask you to perform any database operation (create, find, update, delete), you MUST use the appropriate tools. Do not just describe what you would do - actually execute the operations using the available tools. If you cannot execute the operation due to lack of permissions or roles, you MUST state this clearly in your response.
+
+Important: After your response, the system will call generateObject to convert your output into a structured format according to a specific schema. Therefore:
+ - Provide comprehensive information in your response
+ - Include all relevant data you've gathered or processed
+ - Structure your response logically so it can be easily parsed
+ - Mention any important context, decisions, or actions taken
+ - Include tool execution results in your response`,
+
+  OUTPUT_GENERATOR: `You are a structured output generator for a workflow system. Your role is to convert the provided execution results into a structured format according to a specific schema.
+
+Context: Before this call, the system executed generateText with tools to perform any required actions and gather information. The execution results you receive include both the AI agent's analysis and any tool outputs from database operations, data retrieval, or other actions.
+
+Your responsibilities:
+1. Analyze the execution results from the AI agent (including any tool outputs)
+2. Extract relevant information and data points from both text responses and tool results
+3. Structure the data according to the provided schema
+4. Ensure all required fields are populated with appropriate values
+5. Handle missing or unclear data gracefully by providing reasonable defaults or null values
+6. Maintain data integrity and consistency
+
+Guidelines:
+- Focus on extracting and structuring the most relevant information
+- If the execution results contain tool outputs, incorporate that data appropriately
+- If certain schema fields cannot be populated from the results, use null or appropriate default values
+- Preserve the context and meaning from the original execution results
+- Ensure the output is clean, well-formatted, and ready for workflow consumption
+- Pay special attention to any data returned from tool executions (database queries, record creation, etc.)`,
+};