fix: vscode workspaceState bug workaround

see #301 for writeup, microsoft/vscode@06c07d2 introduces a subtle backwards compatibility issue which causes the extension to be unusable

Author: Anonymous941

src/utils/workspaceHelper.ts

@@ -31,7 +31,7 @@ export async function findSkillFoldersInWs(): Promise<vscode.Uri[]> {
   const askResources = await vscode.workspace.findFiles("**/ask-resources.json");
   const skillFolders: vscode.Uri[] = [];
   askResources.forEach((resourceFileUri) => {
-    skillFolders.push(vscode.Uri.file(path.dirname(resourceFileUri.fsPath)));
+    skillFolders.push(vscode.Uri.file(path.dirname(resourceFileUri.fsPath)).toJSON());
   });
   return skillFolders;
 }
@@ -40,7 +40,7 @@ export function getSkillFolderInWs(context: vscode.ExtensionContext): vscode.Uri
   Logger.verbose("Calling method: getSkillFolderInWs");
   const skillFolders: vscode.Uri[] | undefined = context.workspaceState.get(EXTENSION_STATE_KEY.WS_SKILLS);
   if (doesWorkSpaceExist() && skillFolders) {
-    return skillFolders.length > 0 ? skillFolders[0] : undefined;
+    return skillFolders.length > 0 ? vscode.Uri.from(skillFolders[0]) : undefined;
   }
   return undefined;
 }