Fix recursive files download to use full path as prefix

[RyanRatcliff]

Summary

lo files download <projectId>/path/to/folder/ . --recursive was only using the first path segment as the prefix when listing files, so it downloaded from a higher directory than intended.

Change

• Parse the source into path segments and use the full path after the project ID as the name (prefix) query param when calling the files list API.
• Example: projectId/genomic-archive/snp-array-vcf-Build38/ now correctly filters to genomic-archive/snp-array-vcf-Build38 instead of just genomic-archive.

Testing

• Added a unit test that asserts the list API is called with the full prefix for a multi-segment path.
• yarn test passes.
• Verified locally with a recursive download from genomic-archive/snp-array-vcf-Build38/.

Made with Cursor

[cursor]

PR Summary

Low Risk
Small CLI parsing change plus a targeted unit test; main impact is altering which files are selected for recursive downloads when the source contains multiple path segments.

Overview
Fixes files download --recursive to treat everything after the project/dataset ID as the prefix, instead of only the first path segment, so recursive downloads list and fetch only the intended subdirectory.

Adds a unit test covering multi-segment prefixes (including trailing slashes) to assert the /v1/files list call includes the full name filter.

^{Written by Cursor Bugbot for commit 5518f9e. This will update automatically on new commits. Configure here.}

[github-actions]

🎉 This PR is included in version 13.15.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀