Schema validation is broken for typeless base profiles

[t1m0thyj]

Describe the bug

When using a typeless profile as a base profile and storing tokenValue as a secure field, then schema validation fails.

Expected and actual results

Since typeless profiles are often used as base profiles, I would expect that tokenValue property is supported in them.

For typeless profiles, the first item in the schema array definition gets used which is currently zosmf. We could fix this by re-ordering the schema array to put base profiles first, but will need to consider the impacts of this change.

Describe your environment

Schema created by Zowe CLI v8.0.1
Config edited in VS Code 1.94.1

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.

[t1m0thyj]

If we switch the order, this may break other properties defined in a typeless profile such as encoding.
Ideally IntelliSense for typeless profiles could show all properties available across all profiles, but this might cause conflicts if multiple profiles define the same property (e.g. zosmf user vs zftp user).