fix(build): route server UFS features through data transfer

[LJF-050]

Summary

Route server-native UFS feature selection through curvine-data-transfer while preserving the existing client and CLI feature mappings.

Issue Describe / Design

The server crate split moved UFS composition for server builds into curvine-data-transfer, but the release build script continued to pass curvine-client/<backend> features to the server-only Cargo invocation. Cargo rejected those features because curvine-server no longer exposes the client composition path.

This change selects curvine-data-transfer/<backend> for the server-native scope. Test and client scopes continue to use curvine-client/<backend>, and the CLI scope continues to use curvine-cli/<backend>.

Changes

Area	Change	Impact
build/build.sh	Map server-native OSS-HDFS and OpenDAL backend features to curvine-data-transfer	Server-only release builds resolve UFS features against the crate that now owns server transfer composition
build/build.sh	Preserve existing mappings for test, client, and CLI scopes	Client-facing artifact behavior remains unchanged

Test verified

Test case	Result
bash -n build/build.sh	PASS
Cargo metadata with curvine-data-transfer/opendal-s3,curvine-common/jemalloc	PASS
make format	PASS
cargo build --release -p curvine-server --no-default-features --features curvine-data-transfer/opendal-s3,curvine-common/jemalloc	PASS

Dependencies

• Related PRs: build(release): isolate server-native artifacts (#1243) #1280, fix(build): restore native UFS client artifacts (#1243) #1388, refactor(server): extract data transfer crate (#1243) #1455
• Blocks / blocked by: None