chore: refresh the bundled workspace lock - #63

Closes #62

On the index: nothing on the index moved; this run was forced.

What changed

• Refreshed the bundled minimal workspace uv.lock to the latest within-constraint versions (dlt 1.31.0 → 1.32.0, dlthub 0.30.0 → 0.32.0, dlthub-client 0.28.7 → 0.28.8, fastmcp 4.0.11 → 4.1.8, marimo 0.25.1 → 0.25.2, pyarrow 25.0.1 → 26.0.1), plus 55 transitive updates, dropped async-timeout, backports-tarfile, importlib-metadata, jaraco-classes, jaraco-context, jaraco-functools, jeepney, keyring, more-itertools, pywin32-ctypes, secretstorage, tomli, zipp.
• Synced the bundled minimal workspace dependencies with dlt's workspace_deps(): changed duckdb to duckdb>=0.9,<2.
• Refreshed the root uv.lock to the latest within-constraint versions (beaupy 3.12.0 → 4.0.1, mypy 2.4.0 → 2.4.1, posthog 7.64.1 → 7.87.2, pytest 9.1.1 → 9.2.0), plus 5 transitive updates, dropped emoji, exceptiongroup, tomli.
• Refreshed the bundled skills to workbench 4594950.

Everything unreleased, rather than only what this run moved. The entry is written
against v0.2.11 and replaces the bullets an earlier bump left under
## [Unreleased], so a version pair here may have moved in a bump that is already
merged.

How to check it

make ci ran on run 43252993852 before this branch was pushed,
and runs again on the branch. It covers both lock guards, the scaffold deps guard, the
skills drift guard, the unit and integration suites and the wheel build.

Neither uv.lock is readable as a diff. The entry above is the account of them, and
src/dlthub_init/scaffolds/minimal_workspace/pyproject.toml is what decides what they may resolve to.