Create an AiAgent to take advantage of Action plugins

Problem/Motivation

Currently, AiAgents are explicitly creating actions around narrow use casesContentType, FieldType, TaxonomyAgent to the Drupal assistant. If we can take steps to derive assistant actions through existing API, we can rapidly unlock greater AI coverage without depending on additional downstream work for AI support.

As an example, right now if I were to create a new EntityType in a contrib module, I would have to also define an AiAgent plugin to support assistant actions around that new type. This is less than ideal, especially when the ai_agents module lives outside of core and we are then requiring contrib to support many potential standards.

Proposed resolution

One way to do this would be to derive behavior from existing Action plugins, which already have many of the actions we'd potentially want to do with AI(entity crud, field manipulation, etc), but lack a natural language interface. I think in time this could lead to larger changes upstream in Drupal core(perhaps a standard natural language interface), but for next steps we prove that unlocking Drupal's actions as a natural way to unify the actions layer.

I've attached a list of actions from Drupal CMS with all ECA modules enabled so you can see the overlap in AI behaviors and existing actions.

Remaining tasks

Determine feasibility. Determine means of context negotiation as current actions do not have awareness of contexts required to execute them. Determine how best to explain actions in plain english to AI, as current actions do not have a natural language definition.

User interface changes

API changes

Data model changes