zowe-explorer-vscode: [next] Custom secure properties not loaded

Describe the bug

The ZE extension won’t load a profile (i.e. fails to validate) when provided with a team config that has a profile required property (host, port) in the secure array.

To Reproduce

1. Copy the zowe.config.json (see below) into a new workspace
2. Open the Zowe Explorer on the above workspace
3. Profile gets automatically added, but it’s practically unusable 😢

{
    "$schema": "./zowe.schema.json",
    "profiles": {
        "ibmzosmf": {
            "type": "zosmf",
            "properties": {
                "basePath": "/ibmzosmf/api/v1"
            }
        },
        "base": {
            "type": "base",
            "properties": {
                "port": 1234,
                "rejectUnauthorized": true,
                "tokenType": "apimlAuthenticationToken"
            },
            "secure": [
                "host",
                "tokenValue"
            ]
        }
    },
    "defaults": {
        "zosmf": "ibmzosmf",
        "base": "base"
    },
    "autoStore": true
}

Expected behavior

All properties are loaded regardless of whether or not they are stored securely

Screenshots

Desktop (please complete the following information):

• OS: Windows
• Zowe Explorer Version: #1637
• (Optional) Zowe CLI Version:
• (Optional) Are you using Secure Credential Store?

Additional context

Using a VSIX from #1637