Regenerating schema after plugin install may not include all profile types

[t1m0thyj]

If you have neither the Endevor or Endevor Bridge for Git plug-ins installed and then:

1. Install the Endevor Bridge for Git plug-in first. It will install but fail to validate because the Endevor plug-in is a prereq that is missing.
2. Install the Endevor plug-in second. It will install and update the schema to include new profile types (endevor and endevor-location).

Now you have no plug-in validation errors, but the endevor-bridge-for-git profile type is missing from your schema.
A workaround is to reinstall the Endevor Bridge for Git plug-in (or install any other plug-in that has profiles to trigger a schema update).

[zFernand0]

Related to:

• Add custom schemas provided by extenders to the schema.json file zowe-explorer-vscode#2508

[traeok]

I tested this issue again and it still occurs - however, I'm wondering if we should cancel the installation process for a plug-in if it depends on another CLI plug-in that's not installed?

Update: I wanted to add clarification to a comment I made earlier in standup - VS Code does not prevent users from installing an extension if it has a dependency, but it will install the dependency before installing the requested extension. Maybe we can implement similar behavior? If we cannot reach out to npm, we can warn the user that a dependency is required and cannot be fetched.

[JTonda]

Spike needed: 3 pts
Implementation: Stretch/next PI