Feature Request: Make Cards Transportable and Reusable Across Workspaces

**Summary**
Currently, Cards and their corresponding Card Types are scoped to individual Card Spaces within a single workspace. This limits reusability and portability — valuable structures (like Feature catalogs, System registries, or Idea databases) can’t easily be reused across spaces or other workspaces.

**Problem**
For teams using Huly to model structured data or knowledge (e.g., features, clients, systems), Cards may form a reusable foundation that would be useful across multiple projects or workspaces. However:

- Card Types, Relations, and Tags are defined at the space level.
- There is no export/import, template, or duplication mechanism for Cards or Card Types.
- Recreating Cards manually in new spaces or workspaces is time-consuming and error-prone.

**Suggested Solution**
Implement one or more of the following:

1. **Export/Import mechanism** for Card Types, Cards, and their relationships.

- Allow export to JSON or CSV, including schema definitions and relations.
- Enable import to another workspace or Card Space.

2. **Card Templates** that can be shared globally or workspace-wide.

- Users could “Add from template” when creating new Card Types.

3. **Cross-space referencing or sharing.**

- Allow a Card Space (or individual Card Types) to be made visible and usable in multiple projects or workspaces.

**Use Cases**

- Reuse a standard “Feature” or “Component” Card Type across multiple projects or client workspaces.
- Maintain consistent metadata structures (e.g., systems, environments, teams) in different workspaces.
- Simplify onboarding and workspace setup for multi-client consultants or multi-product teams.

**Impact**
This would significantly improve scalability and consistency for organisations that manage multiple Huly workspaces or long-lived structured knowledge bases.

Keep up the fantastic work!