feat: open Zowe Explorer resources using VSCode URLs

[traeok]

Proposed changes

Enables users to click VSCode URLs directed at our extension. We can parse and handle these URIs to open given resource paths or execute commands (depending on the contents).
For now, I've only added the vscode.open functionality. In the future, we can expose and execute commands if desired.

Example:

• vscode://Zowe.vscode-extension-for-zowe?zowe-ds:/lpar.zosmf/CUSTOMER.PUBLIC.REXX/SAYHELLO
• vscode://Zowe.vscode-extension-for-zowe?zowe-uss:/lpar.zosmf/u/path/to/customer/homedir

Adjust the URLs above to match a Data Set or USS resource under one of your profiles. Then paste the link in your browser to open it within VS Code. Ensure that either:

• this PR is packaged & installed into your copy of VS Code
• you have Dev Host opened w/ this PR and it is the last focused VS Code window

Release Notes

Milestone: 3.1.0

Changelog:

• Added the ability to open VS Code URLs that point to Zowe Resources. #3271
  • Example: vscode://Zowe.vscode-extension-for-zowe?zowe-ds:/lpar.zosmf/TEST.PDS/MEMB will open the MEMB PDS member under the TEST.PDS using the lpar.zosmf profile.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• Enhancement (non-breaking change which adds or improves functionality)
• Breaking change (a change that would cause existing functionality to not work as expected)
• Documentation (Markdown, README updates)
• Other (please specify above in "Proposed changes" section)

Checklist

General

• I have read the CONTRIBUTOR GUIDANCE wiki
• All PR dependencies have been merged and published (if applicable)
• A GIF or screenshot is included in the PR for visual changes
• The pre-publish command has been executed:
  • v2 and below: yarn workspace vscode-extension-for-zowe vscode:prepublish
  • v3: pnpm --filter vscode-extension-for-zowe vscode:prepublish

Code coverage

• There is coverage for the code that I have added
• I have added new test cases and they are passing
• I have manually tested the changes

Deployment

• I have added developer documentation (if applicable)
• Documentation should be added to Zowe Docs
  • If you're an outside contributor, please post in the #zowe-doc Slack channel to coordinate documentation.
  • Otherwise, please check with the rest of the squad about any needed documentation before merging.
• These changes may need ported to the appropriate branches (list here):

[codecov]

Codecov Report

Attention: Patch coverage is 95.45455% with 1 line in your changes missing coverage. Please review.

Project coverage is 93.07%. Comparing base (95320f8) to head (4d41743).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
...kages/zowe-explorer/src/trees/shared/SharedInit.ts	75.00%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3271   +/-   ##
=======================================
  Coverage   93.07%   93.07%           
=======================================
  Files         113      114    +1     
  Lines       11763    11784   +21     
  Branches     2656     2660    +4     
=======================================
+ Hits        10948    10968   +20     
- Misses        813      814    +1     
  Partials        2        2           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[github-actions]

📅 Suggested merge-by date: 11/6/2024

[zFernand0]

haven't tested it yet, but the changes LGTM! 😋

[zFernand0]

LGTM! 😋

I think this will be very useful for sharing links with other people 🙏

Curious if we can add a Copy Full URI Path to the context menus, or on the file tab itself?

[zFernand0]

Thanks for quickly adding the external link option. 🙏

Another question...
Should the search-filter be adjusted (if you click an external link) if there is no search-filter set?

Note: I approved it as-is because I believe it can be merged and these items can be handled in a future PR/issue

[traeok]

Thanks for quickly adding the external link option. 🙏

No problem 😁

Another question... Should the search-filter be adjusted (if you click an external link) if there is no search-filter set?

This seems to be an unrelated issue as these links do not interact with the tree view. Maybe we're setting a description for the profile node at some point during initialization?

Sorry @zFernand0, I misunderstood your question. I think it shouldn't adjust the search filter as an external link is considered a direct lookup of a Zowe resource - it works independently of the tree views and only leverages the FileSystemProvider.

[zFernand0]

Thanks for adding the license headers too 🙏

[anaxceron]

Made a suggestion for edits to the changelog

[anaxceron]

good changelog @traeok!

[t1m0thyj]

LGTM, thanks @traeok!