Feature request: XDRIVE transport (S3 storage backend) support

Is your feature request related to a problem?
Xray-core v26.10.29 shipped the XDRIVE transport with an S3 storage backend (XTLS/Xray-core#7231): the client never connects to the proxy server directly — all traffic flows through an S3-compatible object storage endpoint. Community tests report 20-40 Mbit/s with public cloud storage endpoints.

For self-hosted setups this is also a nice hardening property: the server exposes no inbound ports at all — every connection is outbound, to the storage.

Describe the solution you'd like

• Support network: "xdrive" with xdriveSettings (service s3, endpoint/region/bucket/pathStyle, secrets) when importing JSON server configs.
• VLESS Encryption (the vlessenc dot-string in users[].encryption) parsing alongside "none".
• Ideally: a link format (vless://...?type=xdrive&...) so configs can be shared the usual way.

Describe alternatives you've considered
xray-core itself supports the transport since v26.10.29; the gap is only mobile clients.

Additional context

• XDRIVE S3 merge: XDRIVE transport: Add "s3" storage backend XTLS/Xray-core#7231 (released in v26.10.29)
• Requirements per XDRIVE transport: Require VLESS Multiplex+Encryption; "Google Drive"->"google-drive" XTLS/Xray-core#7182: VLESS + mux + VLESS Encryption, single port

Thank you for Happ — it remains the friendliest client for self-hosted configs.