Zowe Explorer fails to activate if workspace file contains invalid directory path

[adam-wolfe]

Describe the bug

If I open a .code-workspace file that contains a path to a directory that does not exist, Zowe Explorer fails to activate.

To Reproduce

1. Create a workspace file that contains a directory.
2. Modify the workspace file to point to a directory that does not exist.
3. Open workspace from file in VS Code.
4. Check the Extension Host console and notice that Zowe Explorer fails to activate.

Expected behavior

Zowe Explorer should not fail to activate even if the directories listed in the workspace file do not exist.

Screenshots

Desktop (please complete the following information):

• OS:
• Zowe Explorer Version: 3.5.0 (also tested with 3.4.2, which also failed to activate)
• (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]

While I haven't tested it in v2, I believe this issue also exists in that major version, since we pass the first workspace folder as the projectDir regardless of whether it exists.