fix(download): resolve .app bundle paths after archive extraction

[alexpietsch]

Summary

iOS build artifacts from the remote cache are shipped as a tarball containing an application bundle (Something.app), which is a directory on disk. Path resolution after extraction only looked for files whose path ended in .app, so valid caches were never found and the flow failed with “Did not find any installable apps inside tarball.”

Changes

• After extraction, locate iOS installs by recursively finding directories named *.app, without descending into a matched bundle.
• When multiple bundles exist, pick the shallowest path; if depth ties, use lexicographic order on the relative path for a stable choice.
• Android behavior is unchanged: still resolve a real .apk file.

Testing

• Manually tested up-/download of cached packages for both iOS and Android
• Extended __tests__/download.test.ts with cases for shallowest bundle preference and deterministic tie-breaking at the same depth.
• Existing iOS/Android extraction tests continue to cover bundle directory layout, nested layout, and rejecting a plain file named *.app.

[Robert27]

Thanks for your contribution, I'll push a new release soon.