fix(desktop): creating a project from a subfolder selects the existing parent project instead #2660

What happened

When creating a new project, selecting a subfolder located inside an existing parent project folder does not create or select the project using that exact subfolder.

Instead, Maka silently resolves the selection to the existing parent project folder.

How to reproduce

1. Add or create a project in Maka using a parent folder, for example: /path/to/parent-project.
2. Inside that folder, create or locate a subfolder: /path/to/parent-project/child-project.
3. In Maka, choose the option to create/add another project.
4. Select the child-project folder.
5. Observe which folder Maka uses as the project root.

Actual result: Maka selects or opens the existing parent-project.

Expected result: Maka respects the exact child-project folder selected by the user. If nested projects are intentionally unsupported, the UI should explain that constraint instead of silently changing the selection to the parent.

Environment

• Maka version or commit: unknown
• OS and version: macOS (exact version unknown)
• Surface: Desktop

Additional context

This prevents users from managing a nested subfolder as an independent Maka project when its parent folder has already been added as a project.