Vscode-extension-for-zowe: Add support for API Mediation Layer to the Zowe Explorer Connections to further allow the extension stand on its own

[jelaplan]

When creating a new connection, it is not possible to add the base path value. This base path is needed by the API Mediation Layer. A core goal of the original project to add connections was to make Zowe Explorer stand alone and independent of the Zowe CLI. If a user wants to use the API Mediation Layer with Zowe Explorer, she will need to use the CLI to create a workable profile.

When issuing commands or creating profiles on he Zowe CLI, there is an option for base path (e.g., --base-path).

In Zowe Explorer, I tried adding the base path to the URL when creating a profile. I didn't get an error but the path was not added to the profile.

Here is how the prompt appears today.

Here is a design idea

A complication is that the additional text in the instruction may make it harder to read (e.g., /basePath).

Note, both the port and the base path are optional. We don't today convey that the port is optional. If the user doesn't enter a port, the system defaults to 443. Conveying this is tricky because extra instruction text makes it harder to read. Comments?

[MikeBauerCA]

In the CLI, the protocol is not part of the profile (currently https is always used). What does entering the protocol in this case do? This might be a separate issue.

We could use more complex syntax to designate default values and optional parameters but I think we should try to stay simple and more human readable.

Placeholder text: host:port/basePath
Description: Enter a z/OSMF URL in the format host:port/basePath. The default port is 443 and basePath only needs specified when using an API mediation layer.

[jelaplan]

@MikeBauerCA I agree that https should be optional. You are proposing excluding it which I think would be better than making it mandatory and would work more like the create profile in the CLI.

[crawr]

Closed by PR #717