Allow setting visionOS deployment target for appleVisionWithiPadDesign

[freak4pc]

Short description 📝

I reported this issue on Slack and discussed with @waltflanagan, when setting appleVisionWithiPadDesign - you should be able to set a visionOS-specific deployment target.

Otherwise, Xcode defaults to the latest one, which could be 1.1 (even if you want 1.0, for example).

How to test the changes locally 🧐

• Create a project that has iPhone, iPad and appleVisionWithiPadDesign Destinations.
• Set a multiplatform deployment target for iOS & visionOS.
• Before this fix, this yields this error:

I've added tests to cover these areas.

Contributor checklist ✅

• The code has been linted using run mise run lint:fix
• The change is tested via unit testing or acceptance testing, or both
• The title of the PR is formulated in a way that is usable as a changelog entry
• In case the PR introduces changes that affect users, the documentation has been updated

Reviewer checklist ✅

• The code architecture and patterns are consistent with the rest of the codebase
• Reviewer has checked that, if needed, the PR includes the label changelog:added, changelog:fixed, or changelog:changed, and the title is usable as a changelog entry

[freak4pc]

@waltflanagan Check it out when you have a moment. Thanks!

[freak4pc]

Uhm, the tests are passing locally and I can't enter Codemagic to see what it failed on. Isn't it an OSS-centric CI that everyone can see the build failures?

Any thoughts?

[pepicrft]

Uhm, the tests are passing locally and I can't enter Codemagic to see what it failed on. Isn't it an OSS-centric CI that everyone can see the build failures?
Any thoughts?

I'm looking into the Codemagic authorization issue. Regarding the failing builds, it's also a known issue with the Tuist Cloud API. We are looking into it. To prevent it from blocking the merge of this PR, I'll run the workflows locally before merging once @waltflanagan confirms the changes are fine.