Give the Canvas AI Agent knowledge

Overview

One of the things we saw when The University of Edinburgh did tests on the AI Assistant in Drupal CMS 1.0 was that even if the assistant had features to solve things from A to Z, many users still preferred to be able to ask how to solve things from A, then B, then Z and do it themselves.

Canvas is a completely new tool, so the idea of what a component, or a prop or how to put components into other components might not be obvious.

Or you might wonder where a card component goes or what of your components could fit for a specific theme or what the different selections does.

Proposed resolution

1. Define what kind of questions the agent should be able to answer.
2. Create the function calls needed, decide if knowledgebase should be one.
3. Then either:
a. Add the tools and information needed to the orchestration agent
b. (or) create a knowledge sub-agent and decide if that should return directly.

The knowledgebase at this time is so small that RAG or some other requirement should not be needed.

User interface changes

-

Long Term

Add so components can describe in free text what different variations does and other type of data. For now we might add another form where you can fill this in or reuse the one from #3545816: Simple approach to bringing advanced metadata into Canvas AI.