Commit a portable uv.lock (public PyPI URLs)

[IceRhymers]

Follow-up from #3 (PR #16).

Context

Issue #3's acceptance called for a committed uv.lock. It could not be honored: the dev machine's global ~/.config/uv/uv.toml sets the internal Databricks PyPI proxy (pypi-proxy.dev.databricks.com) as the default index, so a locally generated uv.lock embeds proxy URLs that public GitHub Actions runners cannot reach (uv sync times out). pypi.org is also blocked from the dev machine, so a portable (public-URL) lock cannot be produced there.

As an interim fix, #3 untracked uv.lock (added to .gitignore) and CI resolves dependencies fresh against public PyPI on each run.

Goal

Commit a portable uv.lock whose artifact URLs point at public PyPI (files.pythonhosted.org), matching the convention in uc-catalog-mcp / databricks-agent-token-budgets (~93% pythonhosted in their locks), so CI (and any public consumer) can install reproducibly.

Options

• Generate the lock from a network with public PyPI access (no corp proxy), then commit it.
• Or pin a repo-level uv.toml with a public [[index]] default so uv lock produces public URLs regardless of global config.

Acceptance

• uv.lock is tracked again and contains no pypi-proxy.dev.databricks.com URLs.
• Remove the uv.lock entry (and its explanatory comment) from .gitignore.
• CI passes using the committed lock (uv sync against the lock, not a fresh resolve).

Refs: #3, PR #16.