fix(cli): preserve detected iOS target in Builder onboarding

[WcaleNieWolny]

Summary

• map the authoritative Release bundle ID to its matching Xcode application target
• persist the detected target as CAPGO_IOS_TARGET during iOS Builder onboarding
• prevent custom-target projects from falling back to the nonexistent App target during marketing-version handling
• add regression coverage for the Dinnerish / com.dinnerish.app case with multiple application targets

Testing

• bun run cli:check
• focused bundle-ID detector and iOS tail handoff regression tests

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

_{Comment @coderabbitai help to get the list of available commands.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codspeed-hq]

Merging this PR will not alter performance

✅ 43 untouched benchmarks
⏩ 2 skipped benchmarks¹

---

_{Comparing wolny/fix-build-init-ios-target (2cf1dd0) with main (3633ef8)}

Footnotes

1. 2 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[dimin4241-svg]

The selected Xcode target needs to follow the effective provisioning bundle ID.

[dimin4241-svg]

This ignores the effective provisioningBundleId resolved just above. When a user has verified progress.iosBundleIdOverride, the provisioning map is keyed by that override, but CAPGO_IOS_TARGET still comes from the detector’s original Release-ID candidate. In a multi-application project this can make Builder choose one target while supplying a profile for another. Please resolve the target against provisioningBundleId (or omit the override unless they match), and extend the existing override-priority test to assert CAPGO_IOS_TARGET too.