Update global config when a new extender registers with Zowe Explorer

[JillieBeanSim]

Describe the solution you'd like

When a new extender registers with Zowe Explorer we would like to have the global config schema automatically update.

Per @MikeBauerCA:
This direction is similar to how CLI handles it. If a CLI plug-in is installed, only the global schema is updated. Project schemas must be updated via a separate command (either re-init the config or use the zowe config update-schemas command)

---

We can continue to discuss if we would want to allow the user to update the global config file with new type as well as team/user config files some way through the GUI.

OR

Automatically update the global config file with the new type and offer the user a way through the GUI for team/user config and schema

[github-actions]

Thank you for raising this issue.
The community has 30 days to upvote 👍 the issue.
If it receives 10 upvotes, we will move it to our backlog. If not, we will close it.

[crawr]

Research needed: how this update to the schema file on disk will affect CLI plugin. There might also be cases where the extension does not have corresponding CLI schema

v2: nice to have

[zFernand0]

Hey @zowe/zowe-cli-administrators,
Here is a list of possible requirements based on recent discussions:

• Allow schema to be updated simultaneously by different clients
• Avoid replacing global schema with just the contents of ~/.zowe/plugins/plugins.json
  • ZE may need to maintain a list of registered/installed extensions
    • Possibly enhance the plugins.json file to allow VSCEs to be added, OR
    • Add the ability for VSCEs to create and maintain an equivalent extensions.json file
• Handle possible differences between CLI plugin schema and VSCE schema definitions
  • Example: ftp-for-cli may be different than what's expected by ftp-for-ze
• No need to add the ability to update project schema files at this time.

---

Zowe Explorer will need to decide when to call this API based on the design outcome.
Here are some of the possibilities discussed:

• On ZE activation:
  • When all extender VSCEs (e.g. zFTP, CICS, ...) will register asynchronously
• On first use:
  • When the user adds a profile of that type (if there are no extender profiles added yet)
  • When the user right-clicks and Update Profile of that type
• On demand:
  • When the user runs a command (via the command palette)

Note:

• Some of the items above may require this issue to be resolved
  • Missing or wrong schema files can prevent ZE or extenders of ProfilesCache from initializing #1781

---

There was also interest expressed in config init customization. Issues below:

• ConfigBuilder.build IConfigBuilderOpts to accept custom information  zowe-cli#1889
• Config init command to accept custom information when command is run zowe-cli#1418