Create tools (function calls) plugin finder/browser

This issue should go under ai_agents. Hence I have created one and linked the issue.

Work done:

• Correctly process the tools selected in the modal.
• Rebuild the detailed tool usage section when tools are selected.

Remaining work

• Update the save method in ai agent form to handle the data from the modal form on click apply.

To continue with the remaining work, I am a bit confused with the implementation of how to take the values in the modal form on apply click to the ai agent form and save them in the ai agent form?

a.dmitriiev → changed the visibility of the branch 1.1.x to hidden.

a.dmitriiev → changed the visibility of the branch 3519692-create-tools-function to hidden.

a.dmitriiev → changed the visibility of the branch 1.2.x to hidden.

a.dmitriiev → changed the visibility of the branch 1.1.x to hidden.

Yes that may help, the issue is I think we need this Base Tools things figured out. So for me, I think having some Designs of how the Base Tools, Tools API will work is important first and then we want a plugin finder/ browser imo. Base tools may not change the browser that much but I think it might. I also think we want to use AI to help people find the right tool.

Also can we see some designs and screenshots of it here?

Tools form element with 1 tool selected:

Modal dialog that is opened when clicking on "Select tools":

Filtering and selection of tools inside modal dialog:

Tools form element after tool selection:

The tools library is done in the same way the core media library is done, so this design and look should be familiar to all Drupal users.

From a look and feel this is just better than what exists now however:

- It feels mostly a repaint of what exists now. One feedback I got from what exists now is that things like "Modification tools" - Sub-agents tools were confusing to people.
- We have the ability to configure the tools but it appears at the bottom of the page. Which is confusing.
- The UI for configuring the tools is really bad (just having to know the machine names of all bundles for example, know that you would have to limit the content seeder by entity type etc).
- Cannot have multiple versions of the same tool.

However, as mentioned the would get solved with Base Tools.

So given the above is just better in every way than what we have now, happy for this to go in. But it will likely need to be rethought from scratch with base tools