Move sample extensions to separate repo

[t1m0thyj]

Is your feature request related to a problem? Please describe.

The sample extensions may be inconvenient for users to try and for developers to maintain as part of the Zowe Explorer monorepo.

Describe the solution you'd like

Move the samples into their own repo, similar to what Microsoft does with https://github.com/microsoft/vscode-extension-samples

Describe alternatives you've considered

Leave the samples in the monorepo as they are now, but occasionally this may cause our build workflows to break.

Additional context

If we move the samples to a separate repo, we should set up a nightly workflow to ensure they build with the latest ZE API.

[github-actions]

Thank you for raising this enhancement request.
The community has 90 days to vote on it.
If the enhancement receives at least 10 upvotes, it is added to our development backlog.
If it receives fewer votes, the issue is closed.

[t1m0thyj]

Also, the menu-item-sample doesn't need to depend on the Zowe Explorer API. It only uses it for the type IZoweTreeNode. So either we could make the ZE API a dev dep, or stop using it entirely in favor of vscode.TreeItem.

[JTonda]

Consider creating a blog on this.