Zowe schema erroneously flags http as unsupported value for protocol

[roman-kupriyanov]

Describe the bug

When editing my nested profiles in Team Config the "protocol" field erroneously marked as not allowed value, when "http" values are used. At the same time the description of the field shows that HTTP or HTTPS can be used.

An example of the nested profile:

    "tso1": {
      "properties": {
        "host": "test.net",
        "port": 6004,
        "protocol": "http"
      },
      "profiles": {
        "ndvr-v2": {
          "type": "endevor",
          "properties": {
            "basePath": "/EndevorService/api/v2/"
          },
          "secure": []
        },
        <...>
    },
}

After checking the schema, I noticed that only the RSE profile schema includes a protocol field that is limited to "https" only so it may be a reason it erroneously applied to the nested profiles property section.

{
                            "if": {
                                "properties": {
                                    "type": {
                                        "const": "rse"
                                    }
                                }
                            },
                            "then": {
                                "properties": {
                                    "properties": {
                                        "type": "object",
                                        "title": "IBM RSE API Zowe Profile",
                                        "description": "A profile to issue commands to a z/OS system with a working Zowe REST server,Mediation Layer, or IBM RSE (Remote System Explorer) API server installation.",
                                        "properties": {
                                            <...>,
                                            "protocol": {
                                                "type": "string",
                                                "description": "Only HTTPS supported for a TLS handshake to access REST API.",
                                                "default": "https",
                                                "enum": [
                                                    "https"
                                                ]
                                            },
                                        }
}

Expected and actual results

The notification about limited protocols supported should be applied only to the profiles that have this constraint.

Describe your environment

• Zowe CLI version installed (run command zowe --version):

  CLI Version: 8.26.2
  Zowe Release Version: v3.3.0
  

• Installed plug-ins and their version numbers (run command zowe plugins list --short):

  @broadcom/endevor-bridge-for-git-for-zowe-cli@2.7.0
  @broadcom/endevor-for-zowe-cli@8.2.1
  

• Node.js and NPM versions installed (run node --version, npm --version):

  ❯ node --version
  v18.20.8
  ❯ npm --version
  10.8.2
  

• Environment variables in use: N/A
• Operating system and version:

  ProductName:            macOS
  ProductVersion:         15.6.1
  BuildVersion:           24G90
  

• Shell/terminal (bash, cmd, powershell, etc...): zsh
• Daemon mode enabled or disabled: disabled

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

[awharn]

Related to #2302