Ability to Move a Project from One Workspace to Another Workspace

## Problem

Currently, there is no straightforward way to move a project from one workspace to another Huly workspace. This is a significant limitation for organizations that need to restructure, consolidate, or reorganize their workspace and project structure, or when onboarding teams between different workspaces.

## Expected Behavior

Users should be able to:

- Select a project within a Huly workspace and transfer it to another workspace (which they have access to).
- Have all related data (issues, tasks, docs, attachments, custom fields, settings, etc.) preserved and migrated as part of the move.
- Optionally choose to map or remap project members, roles, and permissions in the destination workspace.
- Receive clear feedback and error messages if the move cannot be completed (e.g., due to validation, conflict, or permission issues).
- View an audit log or summary of the migration action.

## Use Cases

- A previously private or internal project is transitioned to open source, necessitating its migration into a public or community workspace
- A personal or hobby project grows in scope and maturity, requiring transfer into a professional, team-managed workspace
- Company or team restructuring across multiple workspaces
- Moving client/customer data between workspaces for organizational, compliance, or access reasons

## Additional Notes

- Huly supports import/export tools and migration helpers for developers, but there is no "one-click" or guided user-facing workflow for this need.