Improve experience for using API ML sessions in Zowe Explorer

[t1m0thyj]

Many users of Zowe Explorer use direct-to-service profiles and store username and password as credentials.
For users of the API ML with SSO and MFA, there are enhancements we could make to provide a more first-class experience.
This epic contains issues to track related bug fixes and feature requests.

Tasks

Beta Give feedback

1. When the default profile has apiml token authentication, other profiles inaccessible vscode-extension-for-zowe#2111
   bug priority-high severity-high +3
   
2. Investigate ZE support for Multi-Factor Authentication vscode-extension-for-zowe#2210
   Research Needed Security priority-medium severity-medium +4
   
3. Search operation does not prompt for login for APIML profile #2259
   enhancement priority-medium +2
   
4. Expand session does not prompt for login for APIML profile #2261
   enhancement priority-medium +2
5. Prevent users being locked out when session has invalid credentials vscode-extension-for-zowe#2262
   bug priority-high +2
   
6. Prevent users from storing wrong credential type for session #2263
   enhancement priority-low +2
7. Support logging in to multiple APIML instances per config file #2264
   enhancement priority-low +2
8. "Log out of authentication service" and "zowe auth logout apiml" Not working #2544
   bug priority-medium severity-medium +3
   
9. Log out from API ML is not available anymore with Manage Profile menu #2633
   bug priority-medium severity-medium +3
   
10. Profile validation assumes token auth for profile using basic auth #2682
    bug priority-medium severity-medium +3

[JillieBeanSim]

Adding this to 24PI2 milestone since is planned for delivery by end of 24Q2 in Roadmap.
@t1m0thyj let me know if that needs to be adjusted since I don't think all of these items are in the plan

[JillieBeanSim]

Hey @t1m0thyj with the Roadmap changing to focus on releases instead of quarters of planning, would you mind updating remaining tasks of the epic to it's planned release milestone. If a milestone doesn't exist, like a 3.x, feel free to create one. Thanks!

[t1m0thyj]

@JillieBeanSim I've updated the milestone for the remaining issues to be V3 Prereleases for issues we plan to address before end of September and V3 GA for issues that can be addressed after V3 is released.

[JillieBeanSim]

@t1m0thyj there will be a new milestone for items after v3 GA, mainly the minor release milestones ie. v3.1.0 (these can be created now if needed). v3 Prerelease should include all breaking changes and included up till last pre-release and v3 GA should include fine tuning items and non breaking change items we want included in the GA.

[JillieBeanSim]

I will keep this epic open for now and remove the milestone with delivery plan extended