chore: remove uv.lock which should not be checked in

From the [documentation](https://docs.astral.sh/uv/concepts/projects/layout/#the-lockfile)

> Unlike the pyproject.toml, which is used to specify the broad requirements of your project, the lockfile contains the exact resolved versions that are installed in the project environment. This file should be checked into version control, allowing for consistent and reproducible installations across machines.
>
> A lockfile ensures that developers working on the project are using a consistent set of package versions. Additionally, it ensures when deploying the project as an application that the exact set of used package versions is known.

The problem with the presence of this `uv.lock` for purposes of development of a library like `deltalake` is that `pip` installations of the released package will _not_ have the contents of that `uv.lock` file.

Therefore I want it to be removed so that our local installations, and CI, are always using `pyproject.toml` to resolve their dependencies in a manner which is consistent with the users of the installed package.

Signed-off-by: R. Tyler Croy <[email protected]>

.github/actions/setup-env/action.yml

@@ -21,9 +21,6 @@ runs:
 
     - name: Install uv
       uses: astral-sh/setup-uv@v3
-      with:
-        enable-cache: true
-        cache-dependency-glob: "python/uv.lock"
 
     - name: Set up Python ${{ inputs.python-version }}
       uses: actions/setup-python@v4

python/.gitignore

@@ -21,3 +21,4 @@ docs/build
 dat-data
 
 wheels/
+uv.lock

python/pyproject.toml

@@ -4,6 +4,7 @@ build-backend = "maturin"
 
 [project]
 name = "deltalake"
+version = "0.22.4"
 description = "Native Delta Lake Python binding based on delta-rs with Pandas integration"
 readme = "README.md"
 license = { file = "licenses/deltalake_license.txt" }
@@ -97,4 +98,4 @@ markers = [
 
 [tool.coverage.run]
 branch = true
-source = ["deltalake"]
+source = ["deltalake"]