Controllable automation for migration of the projects between FlowForge instances

### Description

We need the ability of **continuous delivery (controlled with versioning) between FlowForge instances**.
The snapshot is a great way to represent and distribute the projects, while keep track of projects versions.
Therefore we see the **snapshots** as units to compose the **delivery pack**.

However, the snapshots are not retrievable via API [e.g. at least they come `not fully equipped` via API].

- In general, the objective is to automate continuous delivery between FlowForge instances.

- In particular, the desired feature is related to snapshots “portability” and “redistributivity” to unlock:

- **export snapshot to a JSON**,
e.g. allow admin-level API to extract the snapshot(s) as is, w/o filtering out the “sensitive” parts (flows, settings) as of now.
- This probably breaks the idea “only project-identity-owning representatives can access the flows and settings inside the project”. In that case, the API could be allowed for “project”-token (consider it can be invoked ‘by project’) which won’t break the idea on project exclusive access to its intellectual property.

- **load project from snapshot** (from JSON), via API (it would be also convenient to have this option in UI)

Looking forward to hear your vision on subject of controllable migration of the projects between FlowForge instances

### Have you provided an initial effort estimate for this issue?

I am not a FlowForge team member