Refactor storage integration from MinIO to S3

- Removed MinIO client and related imports from various modules.
- Introduced S3 client and OSS integration for object storage.
- Updated all references to MinIO methods with corresponding S3 methods.
- Added new flowme table schema to the database.
- Adjusted upload and download routes to utilize S3 for file operations.
- Removed obsolete MinIO-related files and routes.
- Ensured compatibility with existing application logic while transitioning to S3.

src/routes-simple/code/upload.ts

@@ -4,8 +4,7 @@ import { router, clients, writeEvents } from '../router.ts';
 import { error } from '../middleware/auth.ts';
 import fs from 'fs';
 import { useFileStore } from '@kevisual/use-config';
-import { app, minioClient } from '@/app.ts';
-import { bucketName } from '@/modules/minio.ts';
+import { app, oss } from '@/app.ts';
 import { getContentType } from '@/utils/get-content-type.ts';
 import path from 'path';
 import { createWriteStream } from 'fs';
@@ -123,7 +122,7 @@ router.post('/api/micro-app/upload', async (req, res) => {
     const minioPath = `private/${tokenUser.username}/${appKey}/${relativePath}`;
     // 上传到 MinIO 并保留文件夹结构
     const isHTML = relativePath.endsWith('.html');
-    await minioClient.fPutObject(bucketName, minioPath, tempPath, {
+    await oss.fPutObject(minioPath, tempPath, {
       'Content-Type': getContentType(relativePath),
       'app-source': 'user-micro-app',
       'Cache-Control': isHTML ? 'no-cache' : 'max-age=31536000, immutable', // 缓存一年