Description

I often find myself in trouble when I handle form extensions. For example, if I'm working with a form and some other dev in the project has created an extension that adds some default options, it's not easy for me to understand where such options come from.
I'm aware there's adebug:form console command, but it's not very useful in this case, because I don't even know that the form (or some of its fields) is extended, and anyway I would be forced to retrieve this information elsewhere, while it could be directly available in the profiler.

I propose to add this information in the form profiler: for each type, a new tab showing the possible extensions of that form type (the tab should be greyed out if no extensions are available)

Example

No response