Add local filesystem-based XDRIVE transport implementation

[Copilot]

Implements the local filesystem-based XDRIVE transport as described in PR #5645 comments, providing a foundation for remote-storage-service-based proxy that can later be extended to Google Drive, OneDrive, etc.

Changes

• transport/internet/xdrive/xdrive.go: Core implementation

  • DriveService interface: Login, Upload, List, Download, Delete
  • LocalDriveService: filesystem implementation using remoteFolder
  • XdriveConnection: bidirectional connection via file polling
  • File naming: {uuid}-{up|down}-{seq} (e.g., 550e8400-e29b-41d4-a716-446655440000-up-0)
  • Client/server role via secrets[0] ("client" or "server")
  • Server polls at 500ms, read polls at 100ms, 10s retention window with auto-cleanup

• infra/conf/transport_internet.go: Config parsing for xdriveSettings

• main/distro/all/all.go: Transport registration

Usage

{
  "streamSettings": {
    "network": "xdrive",
    "xdriveSettings": {
      "remoteFolder": "/path/to/shared/folder",
      "service": "local",
      "secrets": ["client"]
    }
  }
}

Server uses "secrets": ["server"] with the same remoteFolder. Both endpoints communicate through files created in the shared directory.

Original prompt

根据 #5645 (comment) 的描述完成基于本机文件系统（local）的 XDRIVE，对于每个连接在 remoteFolder 内创建名为 uuidv4-up/down-seq 的数个文件，通过 secrets[0] 为 client/server 区分客户端/服务端，新增代码应当全部位于 xdrive.go

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[RPRX]

还真像那么回事，代码收下了没你事了