Profile Not Found Error Handling Regression in Zowe Explorer 3.2.2

[hohy]

Describe the bug

When a profile not configured in the zowe.config.json is used to access a mainframe resource using the FS provider in the ZE version 3.2.2, a wrong error is thrown.

ZE 3.2.2 throws:

{
  code: "Unknown",
  name: "TypeError (FileSystemError)",
  message: "Cannot read properties of undefined (reading 'name')"
}

ZE 3.2.1 throws:

{
  code: "Unknown",
  name: "Error (FileSystemError)",
  message: "Zowe Explorer Profiles Cache error: Could not find profile named: ibmzosmf."
}

It breaks error handling in our extension and we are unable to show correct error dialog to our users.

To Reproduce

Update ZE to version 3.2.2 in VSCode Marketplace.
Try to access mainframe resouce using ZE FS provider:

try {
  const profile = "bad-profile"; // profile that is not configured in zowe.config.json
  const dsn = 'MY.MF.DATASET';
  await vscode.workspace.fs.stat(
    vscode.Uri.parse(`zowe-ds:/${profile}/${dsn}?fetch=true`),
  );
} (err) {
  vscode.window.showErrorMessage(err.message);
}

Expected behavior

I expect the error message in the version 3.2.2 to be same as in the version 3.2.1.

Screenshots

Desktop (please complete the following information):

• OS: MacOS
• Zowe Explorer Version: 3.2.2
• (Optional) Zowe CLI Version:
• (Optional) Do you have secure credentials enabled?
• (Optional) Are you using a custom credential manager?

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.

[traeok]

Dev note: looks like there were some changes to how the profile is loaded from the filesystem that causes all loadNamedProfile errors to be silenced.

Since all loadNamedProfile errors are being silenced, the code in the filesystem continues executing. The "could not find profile" error should stop execution in the filesystem for a non-existent profile (thrown error). We should introduce logic to re-fetch the profile if we were waiting on the profile type to become available