Determine path forward for turning Attributes into JSON schema

Problem/Motivation

This is another "where should it live?" question, and that's the need to normalize tool attributes(specifically inputs and outputs) into JSON Schema. Both MCP and AI function calls will depend on this, though I'm not sure if we can trust the specs to be identical.

Drupal(and Symfony) have normalization capabilities, but I do not yet know that they cover the json schema spec we need. Right now, we are leaning on the normalizer built into the AI module, but then in the case of using this outside of AI(such as MCP) we are creating a dependency on the full module for just one service.

Proposed resolution

Right now I'm leaning toward this living separately in MCP and AI, but I wanted to at least start the conversation somewhere and align on a clear separation of concerns.

Remaining tasks