Set tool operation per tool

@marcus_johansson
I think we should add another column in the tool maintenance section
Something like this

We can have another property $tool_operations, in the confirm form, which stores the mapping b/w tool and operation

That's a good idea!

In case we may use this simple method #3559613-4: Remove dependency on AI/AI Agents module to discover the operation's type dynamically, pre-populating the select box.

I think we should consolidate all tool configuration into a single tools property on the entity. This would eliminate the separate enabled_tools, locked_tools, and tool_operations arrays.

[
  'name' => 'tool_name',                    // Required: tool name
  'description' => 'Tool description',      // Required: tool description
  'input_schema' => [...],                  // Required: MCP tool schema

  // Configuration
  'enabled' => true,                        // Boolean: is tool enabled
  'locked' => false,                        // Boolean: is tool locked
  'operation' => 'read',                    // String: read|write
  
  // Locked definition (only if locked === true)
  'locked_definition' => [
    'name' => 'tool_name',
    'description' => 'Tool description',
    'input_schema' => [...],
  ],
]

To make this more maintainable and type-safe, we should also create dedicated DTOs/Value Objects for this:

ToolCollection - represents the collection of all tools
Tool - represents a single tool with all its configuration
InputSchema - represents the tool's input schema
LockDefinition - represents the locked tool definition
This approach would give us a single source of truth, cleaner code, and better type safety throughout the codebase.

What your though on this.

That's awesome! I opened a new issue for the refactoring #3561170: Consolidate Tool Configuration Into a Single tools Property. Could you take a look at it? Maybe I missed something ...

I propose merging and closing this issue to keep the issue's context clean and separate from the refactoring.