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>

deploy/docker-compose.aliyun-oss.yaml

@@ -0,0 +1,38 @@
+# docker-compose.aliyun-oss.yaml
+# Overlay used when object_storage.provider is aliyun/oss.
+# MinIO is moved behind an inactive profile and app services no longer wait for it.
+
+services:
+  minio:
+    profiles: ["local-minio"]
+
+  minio-init:
+    profiles: ["local-minio"]
+
+  tenant-api:
+    environment:
+      OBJECT_STORAGE_ACCESS_KEY: !reset null
+      OBJECT_STORAGE_SECRET_KEY: !reset null
+    depends_on:
+      minio: !reset null
+
+  worker-generate:
+    environment:
+      OBJECT_STORAGE_ACCESS_KEY: !reset null
+      OBJECT_STORAGE_SECRET_KEY: !reset null
+    depends_on:
+      minio: !reset null
+
+  kol-assist-worker:
+    environment:
+      OBJECT_STORAGE_ACCESS_KEY: !reset null
+      OBJECT_STORAGE_SECRET_KEY: !reset null
+    depends_on:
+      minio: !reset null
+
+  scheduler:
+    environment:
+      OBJECT_STORAGE_ACCESS_KEY: !reset null
+      OBJECT_STORAGE_SECRET_KEY: !reset null
+    depends_on:
+      minio: !reset null