Improve handling of custom and scoped registries for plugin install

[t1m0thyj]

There are several limitations related to how registries are handled for plugin install in V3.

• When installing a scoped plug-in and a scoped registry is defined in npm config, then this scoped registry is not stored in plugins.json so re-installing in a different environment is not reproducible.
• When installing a plug-in from TGZ and a registry is passed on the command line for fetching dependencies, then this registry is not stored in plugins.json because we store the TGZ location instead.
  • In V2 we stored registry instead of location, should we consider reverting to this behavior?
• When installing a scoped plug-in and the scoped registry has credentials stored in project-level npm config, then the credentials are ignored because plugins are installed with ~/.zowe/plugins as the current working directory.

[github-actions]

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