fix(remoteFileSystemProvider): robust project name parsing for special characters

- Improve parseUri to correctly handle project names containing special characters such as [].
- Fallback to query.projectName if path part is missing or empty.
- Ensure decodeURIComponent is used for both path and query extraction.
- This fixes issues where projects with names like "[test]" could not be opened in VS Code.

Author: LaureatePoet

src/core/projectManagerProvider.ts

@@ -128,7 +128,7 @@ export class ProjectManagerProvider implements vscode.TreeDataProvider<DataItem>
                     // get project items
                     const normalProjects = [], trashedProjects = [], archivedProjects = [];
                     for (const project of projects) {
-                        const uri = `${ROOT_NAME}://${element.name}/${project.name}?user=${project.userId}&project=${project.id}`;
+                        const uri = `${ROOT_NAME}://${element.name}/${encodeURIComponent(project.name)}?user=${project.userId}&project=${project.id}`;
                         const status = project.archived ? 'archived' : project.trashed ? 'trashed' : 'normal';
                         const item = new ProjectItem(element.api, uri, element, project.id, project.name, status);
                         switch (status) {

src/core/remoteFileSystemProvider.ts

@@ -100,7 +100,10 @@ export function parseUri(uri: vscode.Uri) {
     const [userId, projectId] = [query.user, query.project];
     const _pathParts = uri.path.split('/');
     const serverName = uri.authority;
-    const projectName = _pathParts[1];
+    let projectName = _pathParts[1] ? decodeURIComponent(_pathParts[1]) : '';
+    if (!projectName && query.projectName) {
+        projectName = decodeURIComponent(query.projectName);
+    }
     const pathParts = _pathParts.splice(2);
     const identifier = `${userId}/${projectId}/${projectName}`;
     return {userId, projectId, serverName, projectName, identifier, pathParts};