chore(tooling): update uv.lock for compatibility with uv>=0.5.22

docs/CHANGELOG.md

@@ -109,6 +109,7 @@ Release tarball changes:
 - ✨ `StateTest` fixture format now contains `state` field in each network post result, containing the decoded post allocation that results from the transaction execution ([#1064](https://github.com/ethereum/execution-spec-tests/pull/1064)).
 - ✨ Include EELS fork resolution information in filled json test fixtures ([#1123](https://github.com/ethereum/execution-spec-tests/pull/1123)).
 - 🔀 Updates ruff from version 0.8.2 to 0.9.4 ([#1168](https://github.com/ethereum/execution-spec-tests/pull/1168)).
+- 🔀 Update `uv.lock` to be compatible with `uv>=0.5.22` ([#1178](https://github.com/ethereum/execution-spec-tests/pull/1178)).
 
 ### 💥 Breaking Change
 

docs/getting_started/installation.md

@@ -4,7 +4,9 @@
 
 The tools provided by [execution-spec-tests](https://github.com/ethereum/execution-spec-tests) use `uv` ([docs.astral.sh/uv](https://docs.astral.sh/uv/)) to manage their dependencies and virtual environment.
 
-`uv` can be installed via curl (recommended; can self-update) or pip (requires Python, can't self-update):
+It's typically recommended to use the latest version of `uv`, currently `uv>=0.5.22` is required.
+
+The latest version of `uv` can be installed via `curl` (recommended; can self-update via `uv self update`) or pip (requires Python, can't self-update):
 
 === "curl"