UX: Improve Extensions settings

[ivanminutillo]

Currently our extensions setting page is designed mostly for technical users (not a casuality it is currently put under "Advanced" section) But extensions on the opposite are mostly designed to allow an higher degree of customisation for non-technical users. There are several layers of confusions atm:

• Bonfire extensions are listed together with external dependencies, schemas and low-level libraries.
• Extensions that can be enabled/disabled are mixed together with others that cannot be removed and it's not obvious what are the ones the user can configure
• Extensions names are not self-explanatory in most cases

Let's take as an example the (great) Obsidian extension page

I think we should:

• [x] List only the extensions that can be toggled and configured in the extension page and put all the other libraries / schema in a separate view (architecture, code overview, or similar)
• [x] Do not put the extensions page under the "Advanced" scary category, but more at the top of the page (extensions is one of the core value prop of bonfire and will be widely used )
• [x] #911
• [x] Add an extension settings page for those extensions that includes advanced config / settings #877

[mayel]

@ivanminutillo this could use some UI improvements but otherwise is basically done (also metadata and icons need to be added to extensions that are missing it)

[ivanminutillo]

I've did quite a bunch of work on the extensions settings. Now data schemas / external libraries are decoupled from the bonfire extensions. The extensions section occupies a specific part in the settings and enabled extensions (that contains settings or subpages) are displaied below the extension section (in the screenshot below)

I've restructured how users and admins can enable extension, using a toggle rather than a series of buttons, also decoupled the logic for users and admins in their respective sections - showing disabled toggles for extensions that only admins can enable - see screenshot.

I've also started drafting an internal page for each extension, if they contains specific settings and options to be configured (still a wip tough)

I think there are still several needed improvements for creating a useful extensions settings:

• [ ] We should remove the distinction between User Interface extensions and feature extensions. This is a developer thing and those pages instead are meant to be used by users (it's not even clear for developers what's the diff at this point).
• [ ] Extensions that cannot be enabled by users should be listed somewhere else