Enhancements to Extensibility APIs

[zFernand0]

As a Zowe Explorer extender, I want these additional enhancements.

• Zowe Explorer unit test suite to review extenders' API methods #1278
• Could ZoweExplorerApi.IMvs also have "Get.dataSet()" ? #693
• API extension for alternative file management and rendering (Callbacks) #601
• Can getQualifedResourceName() be added to extender API ? #745
• Extenders- Opening a Favorite data set results in a document path temp/_D_/Favorites/dataset(member) - the actual profile name is not included  #778
• Please can the session node contextValue include the type of the connection ( "zosmf" / "rse" / "ftp" ) #691
• Can data set tree node contextValue include the "extension" or data set "type"? #686
• Provide an API for appending local file extensions for data set members #1193

In addition to the above issues, we may want to write up some documentation on packages/zowe-explorer-api/docs/API Governance.md:

• Versioning Scheme
• Contribution Guidelines
• Governance and Compliance Rules
  • Internal
  • Verification Scripts
  • External

For more details:

• Publish and support an official Extensibility API with conformance rules #837

[zFernand0]

Since we are talking about processes and governance in this issue, how about standardizing on Changelog keywords (kind of like the Imperative and CLI repos do) 😋