Allow access to Gitpod as an unauthenticated user

Context: Having a method of cloning / starting a project in an unauthenticated manner can value to users onboarding.

Via a non-authenticated flow, we can present to the user upfront how Gitpod works and brings value to them before they are required to hand over their login credentials, this is especially relevant to apps like Gitpod that handle access to sensitive information.

There are many valid reasons why a user would hesitate to sign-up to an app like Gitpod, e.g. the user doesn't want to grant access to their private code, or has other privacy-related concerns around handing over their sensitive data to an unknown entity (Gitpod). I've seen authentication hesitation across many different applications, and lifting authentication requirements to experience the product can sometimes help a user to experience the product in a "risk-free" way.

Experimenting with this idea could be worthwhile.

Examples:

• DAZN allowing users to browse the catalog and see content before logging in.
• Exalidraw allowing you to use the app before logging in.

Challenges

• Disabling elements of terminal access (vscode.dev disables the terminal)
• Preventing abuse (e.g. mining)
• We're not just VS Code browser, and this experience could re-inforce that misconception

Additional information

• Related Twitter thread.
• See vscode.dev

Related to:

• https://github.com/gitpod-io/gitpod/issues/8971

Start by reviewing issue 6967 and the related issue 8971; no implementation files, entry points, or tests are identified in the payload. Define the unauthenticated experience and its handling of terminal access and abuse prevention before implementation can be scoped.