fix(s3): use virtual-hosted style for Aliyun OSS

[overtrue]

Related Issue

Fixes #150.

Background

Issue #150 reports that rc ls aliyun/fenxi-data/ fails against Alibaba Cloud OSS with SecondLevelDomainForbidden.

Alibaba Cloud documents this error as a bucket-scoped OSS request using an endpoint shape that does not include the bucket in the host. Bucket operations need virtual-hosted-style access such as bucket.oss-region.aliyuncs.com.

Root Cause

bucket_lookup = auto was treated the same as path, so rc sent Aliyun OSS object-list requests as path-style requests to the regional OSS endpoint. OSS rejects that shape for bucket operations.

Solution

• Keep explicit --bucket-lookup path and --bucket-lookup dns behavior unchanged.
• In auto mode, detect Aliyun OSS service endpoints like oss-cn-hangzhou.aliyuncs.com and use virtual-hosted-style addressing.
• Preserve path-style auto behavior for custom/local endpoints such as RustFS and MinIO.

Validation

• cargo test -p rc-s3 client::tests:: --lib
• cargo fmt --all --check
• cargo clippy --workspace -- -D warnings
• cargo test --workspace

I could not run against the reporter private Aliyun bucket, but the failing error code, official OSS endpoint rule, and local address-selection tests cover the root cause.