Suggestion: Add core extensions to extension directory

Problem to solve

• confusion about where to find things

Further details

Some things have changed: You used to install the core and then you had the extension manager and TER to install additional third party extensions.

Now, since the subtree split it is not so different for the end user to install additional core components (system extensions) or third party extensions.

Proposal

If extensions.typo3.org is nowadays rather used as a catalog (if I understand it correctly), it might be useful to show all, not just the third party extensions.

Of course, the core extensions should be marked as part of the core to underline that they are supported officially by TYPO3.

What does success look like, and how can we measure that?

• (almost?) all system extensions are searchable in extension directory
• system extensions are clearly marked as system extensions
• if third party extensions depends on system extension, a link is used to link to the sysext in "Dependencies" section
• the composer command is listed for the system extension

Advantages:

• find everything in one place
• easily find Composer command (or package name) for installing a core extension without having to go to packagist
• dependencies to sysexts could be added as links, e.g. see rte_ckeditor_image (depends on rte_ckeditor, this could be a link, as in ext:introduction -> ext:bootstrap_package)

For me, the question is: What is useful for the end user?