chore(ci): retire redundant gitea publish workflow (Forgejo one is authoritative)

Forgejo .forgejo/workflows/publish-python-package.yml already publishes to the
Forgejo PyPI registry. CUST-WP-0059-T01.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

.gitea/workflows/publish-python-package.yml

@@ -1,37 +0,0 @@
-name: Publish Python package
-
-on:
-  push:
-    tags:
-      - "v*"
-  workflow_dispatch:
-
-jobs:
-  publish:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Check out source
-        uses: actions/checkout@v4
-
-      - name: Set up Python
-        uses: actions/setup-python@v5
-        with:
-          python-version: "3.12"
-
-      - name: Install packaging tools
-        run: python -m pip install --upgrade build twine
-
-      - name: Build distributions
-        run: python -m build
-
-      - name: Validate distributions
-        run: python -m twine check dist/*
-
-      - name: Upload to Gitea PyPI
-        env:
-          TWINE_USERNAME: ${{ secrets.GITEA_PACKAGE_USER }}
-          TWINE_PASSWORD: ${{ secrets.GITEA_PACKAGE_TOKEN }}
-        run: >-
-          python -m twine upload
-          --repository-url https://gitea.coulomb.social/api/packages/coulomb/pypi
-          dist/*