Improve "zowe auth login apiml" experience

[adam-wolfe]

Is your feature or enhancement request related to a problem or limitation? Please describe

When an APIML authentication token expires, the user must login to the APIML service again. Logging back into APIML from Zowe CLI causes two things to happen to the user's zowe.config.json file:

1. A new base_apiml_apiml_... profile will be created. Over time this can create a mess in the config file. Maybe this is an issue with how I configure my profiles, but each time I log in, I get a new base_apiml... profile. In zowe.config.json, the default base profile is updated to point to this new base_apiml... profile.
2. Even if a user specifies the --ru false option when logging in, the user has to manually edit their zowe.config.json to add the "rejectUnauthorized": false property to their new base_apiml... profile.

Describe your enhancement idea

1. If a base_apiml profile exists, overwrite it whenever a user logs in again.
2. If the user specifies the --ru false option in the login command, add the "rejectUnauthorized": false property to their base_apiml profile.

Ideally, if I find that my token has expired, I would like to simply reissue zowe auth login apiml --ru false, enter my userid and password, and not have to do anything else related to zowe.config.json.

Provide any additional context

Other considerations:

• The squad is also looking at enabling connections to multiple APIML instances in one config file (Support logging in to multiple APIML instances per config file #1705).

Tested with Zowe CLI versions 7.14.1 and 7.16.4

Screenshots

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

[adam-wolfe]

Duplicate of #1341 and #1650