[FEATURE] Develop concept for various template package states

[eliashaeussler]

Is your feature request related to a problem?

Currently, the Project Builder handles every package template the same way. However, a Composer package can have various states, for example:

• Package is abandoned, see [FEATURE] Demote abandoned packages in template list #461
•  Package is maintained by an official source, e.g. TYPO3 provides a template for TYPO3 projects or extensions

Describe the solution you'd like

We should collect all potential package states and develop a concept about how to handle those. For example, the "official" state of template packages should be reflected in the project template selection.

Describe alternatives you've considered

No response

Additional context

No response

[mteu]

@eliashaeussler Is this something we should keep working on?

[eliashaeussler]

@eliashaeussler Is this something we should keep on working on?

I'd say we keep it open for now, because implementing a routine for official templates is still a thing I consider important. But we should handle this with lower priority, as there are way more important tasks, e.g. #85 and #13 as well as #120 and #512 when it comes to template development and testing.