Template project codespace experience about evidence-vscode

[RandomFractals]

A few notes for the above product and link share to clarify template project in web editor vs codespaces:

• What you see there is Malloy demo project using github.dev version of VS Code Web Editor that runs in a browser, and doesn't use Codespaces with containers to open a github project.
• VS Code Web Editor is a limited version and doesn't support extensions that require node.js services or any other container services.
• Until you have a WASM version of Evidence app dev runtime available, this will not be feasible in the short-term future.
• You can read more about VS Code Web Editor version at: https://code.visualstudio.com/docs/editor/vscode-web
• The current Evidence in GitHub Codespaces delivered in v1.0.0 is the closest we can get to "the everything just works" version of Evidence node.js app in a browser for now.

You can certainly create new/different and simpler try-evidence github project to replicate some of that onboarding flow with GitHub Codespaces today.

I feel like this belongs in the Evidence Template project or elsewhere, as you can reproduce that flow in VS Code extension already today. See #21 for more info.

[RandomFractals]

Closing this as a duplicate of #21. Please review our Codespaces integration in docs and the web editor notes above.

If you'd like to improve the current Evidence project onboarding experience using GitHub Codespaces I would recommend:

• you refine the current template project README.md
• create new try-evidence branch in that template project
• or create new try-evidence project on github, with or without duckdb, etc.

We can link to the new simpler try-evidence project in our Codespaces docs in this extension.

[RandomFractals]

As far as extension is concerned, the remaining "smooth" onboarding experience spit and polish will be addressed in #10 next week. That ticket has sufficient planned feature details already too.

And we just added autoinstall and autostart features on our end to better enable that flow (#53)