Proper extension settings support

[MatthewScholefield]

I noticed lots of extensions either avoid having any settings at all and just hardcode things or roll their own manual settings systems with weird conventions. Has there been any thought of making a standardized settings system for extensions?

I'm thinking something like vscode where there's a standard format in the settings.json but also can have a standard /extension-settings terminal UI or something. I've seen pi-extension-settings but:

1. I failed to get it to work due to some bug (Extension "command:extension-settings" error: Theme not initialized. Call initTheme() first.)
2. Having it be an extension itself means other extensions need to depend on it. Also it's easy for there to be fragmentation if it is not official.

I think pi dev's extension system is a core component to its success. But IMO a key component of a healthy extension system is having these extensions be portable enough to be shared and easy enough to configure.

Anyways, just an idea.
Cheers.