z/OSMF profiles do not respect `protocol` property

[traeok]

Describe the bug

In Zowe Explorer, zosmf profiles defined with the protocol property set to http will not respect said protocol during API requests.

To Reproduce

1. Use a Zowe config that has a z/OSMF profile defined with the HTTP protocol, e.g.:

{
    "profiles": {
        "lpar.zosmf": {
            "properties": {
                "protocol": "http"
            }
        }
    }
}

2. Attempt to send an API request to z/OSMF by listing data sets or USS files
3. Notice that the request either fails or uses the HTTPS protocol

Expected behavior

Profiles in Zowe Explorer should respect the protocol property.

Desktop (please complete the following information):

• OS: Windows 10
• Zowe Explorer Version: 2.14.0

Additional context

The request may not fail if the server supports HTTPS, so it would be best to test with an LPAR or server that only supports HTTP.

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

[traeok]

Update: It turns out that we expect the session-building procedure to happen from the API. z/OSMF profiles did not include the protocol property when building the session object in getStatus. Related issues from non-z/OSMF profiles might be resolved by addressing the logic in the API's respective getStatus implementation.