Fix overrides.CredentialManager:false inconsistencies

[phaumer]

When creating a ~/.zowe/settings/imperative.json file with {"overrides": {"CredentialManager": false}} I can disable secure credentials, which is important for platforms that do not support keytar such as Eclipse Che.

However, that setting is not used systematically and can lead to a lot of user confusion and even incorrect error messages:

• With this file in place and running a zowe config init command it still generates a config file that has secure credentials defined. It should generate a template file without any secure fields.
• When running commands with such secure credentials in the config file one gets errors about not being able to load keytar, which it should not attempt anymore as it was disabled. Instead it should show a warning that secure credentials are disabled and continue the operation by prompting the end user for the missing property values.

As creating such a ~/.zowe/settings/imperative.json file is a bit of a hidden feature I would also propose to

• provide a config init command with a --non-secure option that will generate the settings file as well as create a correct non secure config file
• provide a config init command that allows specifying the name of a custom config file to use instead of the template to support automation, e.g. during Eclipse workspace startup, that can generate these file from a client (such as Zowe Explorer)

[github-actions]

Thank you for creating a bug report.
We will investigate the bug and evaluate its impact on the product.
If you haven't already, please ensure you have provided steps to reproduce the bug and as much context as possible.

[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.