ci: stop artifact upload from failing the build on Gitea runners

Gitea's act_runner does not reliably support the actions/upload-artifact@v4
backend. Drop the artifact upload from the test workflow (the package job's
purpose is to build and smoke-test, not to store wheels) and make the publish
workflow's upload best-effort (continue-on-error) so a flaky artifact backend
cannot block a release — the package is still published to the registry.

.gitea/workflows/publish.yml

@@ -87,6 +87,10 @@ jobs:
         run: uv build
 
       - name: Upload build artifacts
+        # Best-effort: some Gitea act_runner versions don't fully support the
+        # v4 artifact backend. The real deliverable is published to the registry
+        # below, so a failed artifact upload must not fail the release.
+        continue-on-error: true
         uses: actions/upload-artifact@v4
         with:
           name: dist

.gitea/workflows/test.yml

@@ -81,9 +81,3 @@ jobs:
           python -m venv /tmp/server
           /tmp/server/bin/pip install --quiet "${WHEEL}[server]"
           /tmp/server/bin/python -c "import fastapi, uvicorn, aegis_gitea_mcp.server_entry; print('server extra import OK')"
-
-      - name: Upload build artifacts
-        uses: actions/upload-artifact@v4
-        with:
-          name: dist
-          path: dist/*