Goal: allow users to run the slimmest version of wbSuite per default (is this true?) and make them owners of the decision of which extensions they need/want. They should also have an easy mechanism to add or remove extensions to their installation

Current Situation: The list of extensions that we deliver at the moment has been chosen by the original team based on what would support the full Wikibase experience. There is no standard process to add extensions and it may get really cumbersome (users need to build and integrate the code themselves. Documentation may not be available for every extension either). The delivered extensions are on per default.

Open Questions:

• What is the actual user story here?
• should extension management be on configuration level or package level?
• Which extensions to add are we really talking about here? anything made for Wikibase? any other code injection?
• Do we want to make it easy for all the extensions? or we want to create a shortlist of extensions for this?
• Could users just use the pipeline to build their own containers with the extensions they need?
• Do we need an ui for that? (this would increase the complexity a lot)
• What is the upgrade path for users changing the extension set?
• We could map in all extensions via docker volumes? How does the update path look in this case?
• Probably standardized dev user way that is properly documented is enough?