feat(objectstorage): add Aliyun OSS support and auto-detect provider in deploy workflows

Introduces Aliyun OSS as an alternative to MinIO; deploy scripts and CI
workflows now read object_storage.provider from config and conditionally
include or skip MinIO resources in both Docker Compose and k3s paths.
Also adds ops scheduler domain and its migration tables.

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

.gitea/workflows/deploy-config-ci.yml

@@ -45,6 +45,20 @@ jobs:
         run: |
           docker compose -f deploy/docker-compose.yaml config >/tmp/compose.yaml
           docker compose -f deploy/docker-compose.yaml -f deploy/docker-compose.offline.yaml config >/tmp/compose-offline.yaml
+          docker compose -f deploy/docker-compose.yaml -f deploy/docker-compose.offline.yaml -f deploy/docker-compose.aliyun-oss.yaml config >/tmp/compose-aliyun-oss.yaml
+
+      - name: Validate k3s manifests
+        run: |
+          if ! command -v kubectl >/dev/null 2>&1; then
+            echo "kubectl not found; skipping kustomize manifest validation."
+            exit 0
+          fi
+          kubectl kustomize deploy/k3s >/tmp/k3s.yaml
+          kubectl kustomize deploy/k3s-aliyun-oss >/tmp/k3s-aliyun-oss.yaml
+          if grep -Eq 'name: (minio|minio-init)$' /tmp/k3s-aliyun-oss.yaml; then
+            echo "aliyun object-storage overlay must not render MinIO resources"
+            exit 1
+          fi
 
       - name: Smoke build server runtime image
         run: |