ci: pin uv, the tool that builds the pytest venv

The panel backend has 25 pytest tests that no workflow has ever run. Making
them run needs a throwaway virtualenv, and uv is what builds it in seconds
against the pinned requirements-dev.txt.

Installing it through install-ci-tools.sh rather than assuming it is on the
runner keeps the version in one place, where the other three tools already
live, and where the Renovate regex manager can move it.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

renovate/k8s/configmap.yaml

@@ -93,6 +93,14 @@ data:
           "datasourceTemplate": "github-tags",
           "depNameTemplate": "yannh/kubeconform"
         },
+        {
+          "customType": "regex",
+          "description": "uv version used to build the pytest venv",
+          "managerFilePatterns": ["^\\.gitea/workflows/tool-versions\\.env$"],
+          "matchStrings": ["(?:^|\\n)UV_VERSION=\"(?<currentValue>[0-9.]+)\""],
+          "datasourceTemplate": "github-tags",
+          "depNameTemplate": "astral-sh/uv"
+        },
         {
           "customType": "regex",
           "description": "stakater/reloader chart version pinned in the deploy workflow",

renovate/renovate.json

@@ -82,6 +82,14 @@
       "datasourceTemplate": "github-tags",
       "depNameTemplate": "yannh/kubeconform"
     },
+    {
+      "customType": "regex",
+      "description": "uv version used to build the pytest venv",
+      "managerFilePatterns": ["^\\.gitea/workflows/tool-versions\\.env$"],
+      "matchStrings": ["(?:^|\\n)UV_VERSION=\"(?<currentValue>[0-9.]+)\""],
+      "datasourceTemplate": "github-tags",
+      "depNameTemplate": "astral-sh/uv"
+    },
     {
       "customType": "regex",
       "description": "stakater/reloader chart version pinned in the deploy workflow",