Create `canary` branch + separate canary docs from release docs

[resir014]

Description

Currently, the release docs is jumbled up with the canary docs. To implement a proper canary release process, like in Vercel's repos, a separate canary branch should be created, and all canary releases are tagged from there.

This means the master branch will only contain production-ready code, which also allows us to easily merge in hotfixes when needed.

Implementation Model

• Create a canary branch
• Create a separate preview URL for canary components in Vercel
• Tag all future canary releases in the canary branch