Update toolbelt to new cookieless Storefront model

[tamorim]

Let's kill the cookie! 🔪
Here's the to-do list:

watch

• We're going to use WebSockets (SignalR) for communication with Storefront when running watch
• Specific headers will be passed, containing e-mail, account and the app: x-vtex-user=<developer-email>, x-vtex-account=<account> and x-vtex-app=<vendor>.<app-name>
• watch will no longer need a sandbox name, instead it will use an optional argument that will indicate the Workspace which the developer environment will be mirrored (Watch with an optional argument for setting the workspace #62)
• Provide a URL for sharing the developer environment. It will follow like this: <store-url>/?workspace=sb_<developer-email>
• Check if a workspace of the format sb_<developer-email> exists, if not, create it

login

• The login will need an argument, this argument is the account of the store
• Keep the account name somewhere
• Can only be logged on 1 account at a time

[klzns]

Check if a workspace of the format sb_developer_email exists, if not, create it

@amoreira @tamorim I think Toolbelt should always try to create a workspace and if it exists, the API should throw an error.

[tamorim]

Para obter uma lista de Workspaces:

http://api.beta.vtex.com/<account>/workspaces

Para criar é a mesma rota, só que um POST

Headers:

ACCEPT application/vnd.vtex.gallery.v0+json
AUTHORIZATION token <token>

Para criação, o body da request tem que ser:

{ "name": "sb_<developer-email>" }

[klzns]

What happens if it sends a POST with a sandbox that is already created? @amoreira

[tamorim]

@BrenoC It doesn't give an error, but returns a message warning that the workspace it's already created.