Add shortcuts to the context menus to allow keyboard access

[jelaplan]

Add shortcuts with icons in the context menus. Many of the actions in the Zowe Explorer are only available through right click context menus. Adding shortcut key combinations and echoing those shortcut key-combinations in the menu provide an alternative and faster way to interact with the extension. The VS Code built in file explorer has these shortcuts and icons. I drew up these  design ideas in the mockups I delivered.

Dataset

Member

[jelaplan]

Here is how the built in explorer for VS Code looks

[katelynienaber]

Working on this. Seems that if you execute a command from a keybinding, VSCode does not receive the proper context for the focused item in the tree, and any command using the context to decide whether it is allowed to run won't run: https://github.com/microsoft/vscode/issues/72442

Maybe there is a workaround. I will spend some more time on it.

[lauren-li]

Even if VS Code issue https://github.com/microsoft/vscode/issues/72442 prevents Zowe Explorer from effectively implementing keybindings at the moment, perhaps we should go ahead and compile a list of keybindings we want to use, so that we'll be ready to implement them when the bug is fixed. Additionally, we can then provide this list to extenders in our conformance criteria to let them know what keybindings to avoid using.

[lauren-li]

@tomofbroadcom When you work on a proposed list of keybindings for Zowe Explorer commands, you may want to start with the commands in the below screenshot (from PR #1308), as these would be keybindings we are more likely to be able to implement immediately (i.e. without waiting for the bug mentioned above to be fixed):

[github-actions[bot]]

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

[JillieBeanSim]

This enhancement has had no community activity for 12 months. The issue also has less than 10 up-votes by the community. No action on this enhancement is targeted for the next 2 calendar quarters. Therefore, this enhancement is being closed. If you feel that this enhancement should continue to be available for community up-votes, you may reopen this issue.