Profiles shouldn't have import of vscode in ZE API

[JillieBeanSim]

An import for vscode was brought into 3.4.2 in the Profiles section of ZE API which should not happen as it can break cli plugins that use our ZE API profile management classes and methods

zowe-explorer-vscode/packages/zowe-explorer-api/src/profiles/AuthHandler.ts

Line 17 in e95fb9a

import * as vscode from "vscode";

Describe the bug

To Reproduce

Expected behavior

Screenshots

Desktop (please complete the following information):

• OS:
• Zowe Explorer Version:
• (Optional) Zowe CLI Version:
• (Optional) Do you have secure credentials enabled?
• (Optional) Are you using a custom credential manager?

Additional context

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

[zFernand0]

Thanks for the discussion during standup today.

I was mostly trying to understand the implication of CLI Plug-in developers having the Zowe Explorer API packages as a dependency.

And on that note, I would like to quote what we document on public NPM regarding our intentions with this package.

Please note: These capabilities are built for use in (and alongside) Zowe Explorer

---

Hey @phaumer,
Wanted to get your thoughts on the above 🙏

Going forward, we were thinking making this more explicit in the conformance criteria for V4.
And in the meantime, we could resolve this by adding a wrapper and automated tests to prevent this from happening in the future.