Fix: use --arch instead of --triple for Swift universal build in Codemagic

[m13v]

--triple arm64-apple-macosx on Xcode 16.4 running on an arm64 host (mac_mini_m2) places the binary in .build/release/ (native, non-arch-prefixed) instead of .build/arm64-apple-macosx/release/. This caused the "Create universal app bundle" step to fail immediately with "ERROR: Missing built binaries".

Fix: Replace --triple arch-apple-macosx with --arch arm64 / --arch x86_64, which reliably outputs to .build/arm64-apple-macosx/release/ and .build/x86_64-apple-macosx/release/ regardless of host architecture.

[greptile-apps]

Greptile Summary

This PR fixes a Swift build issue in the Codemagic CI/CD workflow where binaries were being placed in the wrong directory on Xcode 16.4 running on arm64 hosts.

• Changed Swift build flags from --triple arm64-apple-macosx and --triple x86_64-apple-macosx to --arch arm64 and --arch x86_64
• Ensures build outputs are consistently placed in .build/arm64-apple-macosx/release/ and .build/x86_64-apple-macosx/release/ regardless of host architecture
• Resolves the "Missing built binaries" error in the universal app bundle creation step

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The change is minimal (2 lines), well-documented, and addresses a specific build failure. The --arch flag is the correct Swift build parameter and ensures consistent build output paths across different host architectures. No logic changes or potential side effects.
• No files require special attention

Important Files Changed

Filename	Overview
codemagic.yaml	Replaced --triple with --arch flag for Swift builds to ensure consistent output paths across different host architectures

_{Last reviewed commit: b373d26}

[gemini-code-assist]

Code Review

This pull request addresses a build failure in the Codemagic CI pipeline for the Swift macOS application. The change replaces the --triple flag with --arch for the swift build commands. This ensures build artifacts are placed in predictable, architecture-specific directories, which is necessary for the subsequent step that creates a universal binary. The fix is correct and effectively resolves the issue.