CLI: allow v1 state files to be generated #1227
Description
I'm trying to work out whether this is worthwhile
The ask is: is there some way I can eject a Project as v1 state? Maybe checkout --format state -o state.json?
The benefit is: users can use the established and very stable v1 sync to deploy their projects is something goes wrong in v2
The problem is: it's not just a state file you need to deploy - you need a config object and a project.yaml file. And I don't want to write generators for them
The counterpoint is: assuming we're converting between v2 and v1 state properly, there isn't actually much logic in deploy we need. We just post the state file. So it's probably better to just fix any issues in state conversion?