fix(cli): specify 2.x version ranges for dependencies

[rexxars]

Description

When bootstrapping new studios using the Sanity v2 CLI, you currently get the following error:

Error: No "sanity.json" file found in plugin "@sanity/vision"

This is caused by the CLI installing the v3 version of @sanity/vision, because we specify that we want latest. Theoretically all the other dependencies have the same issue - the only reason they work is because we no longer use these modules in v3, and so latest still points to the v2 version.

This PR changes to use version ranges (^2.0.0) for everything (and drops resolving the latest version, since it is irrelevant), which should ensure that even if we do release new versions of these packages, it won't break anything in v2 studios.

[sc-28222]

What to review

• You are able to bootstrap new v2 studios with v2 dependencies

To test:

• Check out the branch
• Use node 14
• Install dependencies (yarn)
• Build the monorepo (yarn build)
• Initialize a new project (~/path/to/monorepo/packages/@sanity/cli/bin/sanity init)
• Check that it installs dependencies and you can run sanity start

Note: CI fails because of this exact issue, ironically.

Notes for release

• Fixed issue where new v2 studios failed to be created because of the incorrect @sanity/vision version being installed

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated
studio-workshop	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Dec 19, 2022 at 7:00PM (UTC)
test-studio	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Dec 19, 2022 at 7:00PM (UTC)