fix: deprecate minio and introduce s3 storage backend

docs/content/en/_index.md

@@ -21,7 +21,7 @@ Save Any Bot is a tool that allows you to save files from Telegram to various st
 - Automatic organization based on storage rules
 - Supports multiple storage backends:
     - Alist
-    - Minio (S3 compatible)
+    - S3
     - WebDAV
     - Telegram (re-upload to specified chat)
     - Local disk

docs/content/en/deployment/configuration/_index.md

@@ -79,7 +79,7 @@ Each storage endpoint requires at least the following fields:
   - `local`: Local disk
   - `alist`: Alist
   - `webdav`: WebDAV
-  - `minio`: MinIO (compatible with S3 API)
+  - `s3`: aws S3 and other S3 compatible services
   - `telegram`: Upload to Telegram
 
 Example, this is a configuration that includes local storage and webdav storage:

docs/content/en/deployment/configuration/storages.md

@@ -41,17 +41,18 @@ password = "your_password" # Password for WebDAV
 base_path = "/path/to/webdav" # Base path in WebDAV, all files will be stored under this path
 ```
 
-## MinIO (S3)
+## S3
 
-`type=minio`
+`type=s3`
 
 ```toml
-endpoint = "minio.example.com" # Endpoint for MinIO or S3
-access_key_id = "your_access_key_id" # Access key ID for MinIO or S3
-secret_access_key = "your_secret_access_key" # Secret access key for MinIO or S3
-bucket_name = "your_bucket_name" # Bucket name for MinIO or S3
+endpoint = "s3.example.com" # Endpoint for S3
+region = "us-east-1" # Region for S3
+access_key_id = "your_access_key_id" # Access key ID for S3
+secret_access_key = "your_secret_access_key" # Secret access key for S3
+bucket_name = "your_bucket_name" # Bucket name for S3
 use_ssl = true # Whether to use SSL, default is true
-base_path = "/path/to/minio" # Base path in MinIO, all files will be stored under this path
+base_path = "/path/to/s3" # Base path in S3, all files will be stored under this path
 ```
 
 ## Telegram