Fix Python setup in Gitea Actions workflows

The oci-mcp-runner uses node:20-bookworm which runs as root and does
NOT ship with sudo installed. Our workflows used 'sudo apt-get' → step
failed with 'sudo: command not found' (exit 127) on first invocation
of sku-catalog-refresh.yaml.

Fix both affected workflows (sku-catalog-refresh + kb-health):
- Drop the `sudo` prefix (we're already root).
- Install Python deps via apt packages (python3-requests, python3-yaml,
  python3-bs4) instead of pip. Avoids PEP 668 / externally-managed
  environment error on Debian 12 and is faster/cacheable by the runner.

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

.gitea/workflows/sku-catalog-refresh.yaml

@@ -41,9 +41,9 @@ jobs:
 
       - name: Setup Python
         run: |
-          sudo apt-get update -qq
-          sudo apt-get install -y python3 python3-pip jq
-          python3 -m pip install --user requests pyyaml
+          apt-get update -qq
+          apt-get install -y --no-install-recommends python3 python3-requests python3-yaml jq
+          python3 --version
 
       - name: Refresh prices from Oracle API
         id: refresh