Extensions settings group naming

[VGRSTM]

Today each contributed extension may promote some contributions to settings:
"contributes": {
"configuration": {

The way extension's settings item(s) are promoted to GUI is adding a dedicated group to Extensions top most category. Group naming per my understanding is today based on configuration contribution ID playing with camel case parsing.

As example:
myExtension.choice1 is going to be rendered promoting a My Extension group as child of Extensions

Funny stuff is extension contribution is allowing a category title but this one seems not being taken into account at all today
"contributes": {
"configuration": {
"type": "object",
"title": "A Nice Contribution",
"properties": {
"myExtension.choice1": {

What do you think (I may contribute to if ok) decoupling IDs and rendering ? Any foreseen drawback (namespace control like or ...) ?
Title being free text it would ease too proper control of promoted UX.

PS: Today Theia doesn't behave the same as VSCode