ci: replace Django CI with Python-native workflow for Werkzeug

The previous `django.yml` incorrectly assumed a Django project structure.  
This change replaces it with a generic Python CI workflow that:
- Uses `pytest` (or `unittest`) instead of `manage.py test`
- Removes Django-specific assumptions
- Supports multiple Python versions (3.8–3.11)
- Installs the package in editable mode for accurate testing

This aligns the CI setup with Werkzeug’s actual architecture as a WSGI utility library, not a Django application.

Author: Umair Siddiquie

.github/workflows/ci.yml

@@ -0,0 +1,35 @@
+name: Python CI
+
+on:
+  push:
+    branches: ["main"]
+  pull_request:
+    branches: ["main"]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.8", "3.9", "3.10", "3.11"]
+      fail-fast: false
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install -e .
+          # If you have test-specific deps, add them too:
+          # pip install -r requirements-test.txt
+
+      - name: Run tests
+        run: |
+          # Werkzeug projects typically use pytest or unittest
+          python -m pytest  # or: python -m unittest discover