imperative: ProfileInfo APIs do not isolate operations by layers

[zFernand0]

Describe the bug

In Zowe Explorer, it is possible to need some degree of isolation between layers in a loadedConfig, even when homeDir and projectDir are specified.

Assume the following config files.

// ~/.zowe/zowe.config.json
{
  "profiles": {
    "global_apiml": { "type":"zosmf", "properties": {"basepath": "global" } },
    "global_base":  { "type":"base",  "properties":{"host":"LPAR_111", "port": 1234, "tokenValue":"XYZ"} },
  },
  "defaults": { "zosmf": "global_apiml",  "base": "global_base" }
}

// ~/Desktop/myProjectDir/zowe.config.json
{
  "profiles": {
    "project_apiml": { "type":"zosmf", "properties": {"basepath": "project" } },
    "project_base":  { "type":"base",  "properties":{"host":"LPAR_222", "port": 5678, "tokenValue": "ABC" } },
  },
  "defaults": { "zosmf": "project_apiml",  "base": "project_base" }
}

Expected and actual results

Assuming this pseudoCode below

const pi /*profile info instance */ = new ProfileInfo("zowe");
await pi.readProfilesFromDisk({ homeDir: "~/.zowe", projectDir:"~/Desktop/myProjectDir" });
const globalApiml = pi.getAllProfiles("zosmf").find(prof => prof.name === "global_apiml");
const profileArgs = pi.mergeArgsForProfile(globalApiml);

I would expect profileArgs to be:

{
  "basepath": "global",
  "host": "LPAR_111",
  "port": 1234,
  "tokenValue": "XYZ"
}

but instead we get:

{
  "basepath": "global",
  "host": "LPAR_222",
  "port": 5678,
  "tokenValue": "ABC"
}

Describe your environment

Zowe V3
Zowe CLI (and SDKs): v8.6.0

Additional context

Related to:

• Token related operations may cause invalid profiles when multiple layers are involved zowe-explorer-vscode#3011

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