[next] ProfileInfo needs schema/meta files to exist

[t1m0thyj]

In order for ProfileInfo to check for missing args, it requires schema files to exist for team config and meta files to exist for old school profiles. This requirement may be unavoidable, however there are a few concerns we may need to address:

• How will these schema files be created for users of apps developed with the ProfileInfo API? Zowe CLI shouldn't be a requirement for bootstrapping a working team config environment.
• How will these schema files be updated when a profile definition changes? This has been a problem in zowe-v1-lts CLI, e.g. when the --protocol option was added to z/OSMF profiles but was still missing from meta files.

[zFernand0]

How will these schema files be created for users of apps developed with the ProfileInfo API?

I believe there is an updateSchema method that app developers can call whenever they get new profile information (like when an extension gets installed on VSCode and registers to Zowe Explorer). ⚠️ I believe we still have the problem of different applications possibly overriding each other's schemas though.

How will these schema files be updated when a profile definition changes?

That something we still need to figure out (for V3 maybe?)

[JTonda]

The intention is for the profile info apis to work without schema.json file.