Feature Request: Support "Import Data" at Folder Level for Microservice Project Workflows

Description:

Currently, the "Import Data" feature in yaak operates at the Workspace level as the base unit. While this design works for general cases, it creates a significant workflow friction in microservice-based projects.

In real-world microservice development, a single project typically consists of multiple independent services. Each service often maintains its own OpenAPI specification (e.g., openapi.json). The standard and intuitive workflow is to organize these related service definitions within a single Workspace, grouped under different folders.

However, the current implementation forces users to create a new Workspace for every imported file or data source. This leads to a fragmented structure where related microservice APIs are separated across multiple workspaces, which contradicts the logical organization of a unified project.

Proposed Solution:

Add support for a "Import Data" option on the right-click context menu of a Folder.

Expected Behavior:

1. User right-clicks on a target folder inside an existing Workspace.

2. A context menu appears with an option: "Import Data" (or "Import into this Folder").

3. Selecting this option opens the import dialog (same as the existing one).

4. The imported content (e.g., an openapi.json file from Service A) is placed directly into the selected folder, not into a new Workspace.

5. This allows a single Workspace to neatly contain folders like service-a, service-b, each holding its respective imported API definitions.

Benefits:

• Logical Project Structure: Aligns with the microservice architecture pattern, keeping all services of one project under one Workspace roof.

• Improved Workflow Efficiency: Eliminates the need to manually move items after import or manage an excessive number of workspaces.

• Industry Standard Parity: This behavior is the established norm in mature API tools like Postman and Apifox, where import targets a specific collection or folder. Matching this pattern reduces the learning curve for users migrating from these platforms.

• Enhanced Organization: Provides users with the flexibility to structure their Workspace as they see fit (by project, by team, by environment) without being constrained by the import mechanism.

Example Use Case:

• Project: "E-Commerce Platform"

• Workspace: "E-Commerce Platform APIs"

• Folders: user-service, product-service, order-service, payment-service.

• Current Pain Point: Importing user-service-openapi.json creates a new Workspace. The user must then manually move it into the desired folder within the main project Workspace.

• With Feature: User right-clicks the user-service folder, selects "Import Data", chooses the file, and it appears directly inside that folder.

Conclusion:

Implementing folder-level import would significantly enhance yaak's usability for team-based and microservice development scenarios, bringing it in line with user expectations and industry-standard workflows.

Thank you for considering this enhancement to improve the developer experience in yaak.