Quickstart now uses DuckDB WASM instead of CLI

[rmoff]

• Update Quickstart to use DuckDB WASM
• Updated samplerepo README to use DuckDB WASM

Linked Issue

Closes #6076

---

Change Description

Background

See #6076 and #6001

New Feature

The Quickstart (both docs, and samplerepo) now uses the DuckDB that is integrated in the lakeFS UI for all data manipulation including writing back to lakeFS. Previously this had to be done through the DuckDB CLI which we shipped as a Docker image. #6044 added the necessary functionality to DuckDB-WASM so now we will use it in the quickstart.

Testing Details

Manually

[github-actions]

🎊 PR Preview a8b026a has been successfully built and deployed to https://treeverse-lakeFS-preview-pr-6092.surge.sh

🕐 Build time: 0.015s

_{🤖 By surge-preview}

[ozkatz]

Still in draft, I know but:

1. this looks GREAT and definitely simplifies things
2. the screenshot at the bottom of commit-and-merge still uses LAKEFS_OBJECT() so should be replaced.
3. One suggestion: except for reverting which is a relatively advanced function, the rest (branching merging and committing) could be done directly in the UI too. Perhaps at some point we want to show tabs (UI, CLI) so that users could try out a simpler way if they are not terminal savvy? (not for this PR obviously)

[rmoff]

• this looks GREAT and definitely simplifies things

Thanks 😄

• the screenshot at the bottom of commit-and-merge still uses LAKEFS_OBJECT() so should be replaced.

Fixed (and another one like this too)

• One suggestion: except for reverting which is a relatively advanced function, the rest (branching merging and committing) could be done directly in the UI too. Perhaps at some point we want to show tabs (UI, CLI) so that users could try out a simpler way if they are not terminal savvy? (not for this PR obviously)

Good idea. Logged #6103

[rmoff]

Tested manually against both 0.104.0 (Docker) and build from current master. Previous DuckDB gremlins have been vanquished and this PR is good to go.

[arielshaqed]

Neat!

Is there any way to keep an explanation of access keys around? Probably towards the end of the quickstart -- so readers will be able to get started with their own tools.

In general I think we might make it clear that DuckDB is only one tool that works with lakeFS. I really like lakeFS for being a tool rather than a framework, and prefer that our messaging (also) explain that. I realize that this is a lot to ask, especially of a quickstart.

[rmoff]

thanks @arielshaqed -- logged your suggestion and will triage & track :)