Add list of hooks and tools when fetching plugins

[zAlweNy26]

Description

In this way, you can visualize in the frontend or from a generic client, the used hooks by each plugin and their priority, for a better understanding of the flow of the plugins you installed. You can also see the tools created by the plugins.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas

[pieroit]

This is a good idea thanks
What about adding the tools?

[zAlweNy26]

I thought about that too, but... who cares about the tools names? The description of the plugin should already answer a hypothetical question like "how do I trigger this plugin?", or am I wrong?

[zAlweNy26]

Also added tools, should the entry be called used_tools, tools or created_tools?

[zAlweNy26]

I was thinking about changing the data structure in this way, where the key is the priority:

{
  "0": ["hook name 1", "hook name 2"],
  "1": ["hook name 3", "hook name 4"]
}

(Suggested by the Cat 😉)

[pieroit]

I was thinking about changing the data structure in this way, where the key is the priority:

{
  "0": ["hook name 1", "hook name 2"],
  "1": ["hook name 3", "hook name 4"]
}

(Suggested by the Cat 😉)

The previous was better, because it makes no assumptions on ordering or indexing.
Two keys tools and hooks with a list of dicta inside