ci: unique qdrant container name per run — parallel workflows on one host clash

Two concurrent jobs (docker-build + PR Checks on the same push) both
used container name 'qdrant'; the second job's 'docker rm -f qdrant'
destroyed the first job's Qdrant mid-run, so the test collection 404'd.
Name is now qdrant-${{ github.run_id }} everywhere (cleanup included).

.gitea/workflows/cron.yaml

@@ -37,11 +37,11 @@ jobs:
 
       - name: Cleanup old Qdrant container
         run: |
-          docker rm -f mcp-maildir-ci-qdrant 2>/dev/null || true
+          docker rm -f qdrant-${{ github.run_id }} 2>/dev/null || true
 
       - name: Start Qdrant
         run: |
-          docker run -d --name mcp-maildir-ci-qdrant \
+          docker run -d --name qdrant-${{ github.run_id }} \
             --network "container:$(hostname)" \
             docker.io/qdrant/qdrant:latest
 
@@ -68,7 +68,7 @@ jobs:
 
       - name: Cleanup Qdrant
         if: always()
-        run: docker rm -f mcp-maildir-ci-qdrant || true
+        run: docker rm -f qdrant-${{ github.run_id }} || true
 
   build-push:
     needs: [test, integration-test]