fix(cli): wrong export methods for iOS building (#11092)

[jmilesj]

Current export methods for iOS building is not correct, closes #11092

According to https://developer.apple.com/documentation/xcode/distributing-your-app-for-beta-testing-and-releases#Create-a-custom-distribution, the full list of available options are:

• App Store Connect (app-store)
• Ad Hoc (ad-hoc)
• Enterprise (enterprise)
• Developer ID (Documented, but actually not a legal option)
• Development (development)
• Copy App (Documented, but actually not a legal option)
• Validation (validation, not documented, but Apple says it's a legal option if we try to create an achieve via cli)

Unfortunately, the documentation from Apple and the actual behavior does not match.

Given that one can only pick the four options from the Organizer app when uploading an app to app store connect, I'm defining export methods only with those four.

[github-actions]

Package Changes Through d177f7c

There are 3 changes which include @tauri-apps/cli with patch, tauri-cli with patch, tauri with patch

Planned Package Versions

The following package releases are the planned based on the context of changes in this pull request.

package	current	next
tauri	2.5.0	2.5.1
@tauri-apps/cli	2.5.0	2.5.1
tauri-cli	2.5.0	2.5.1

Add another change file through the GitHub UI by following this link.

---

Read about change files or the docs at github.com/jbolda/covector

[lucasfernog]

if you run xcodebuild -help in the terminal you get this:

method : String

		Describes how Xcode should export the archive. Available options: app-store-connect, release-testing, enterprise, debugging, developer-id, mac-application, and validation. The list of options varies based on the type of archive. Defaults to debugging. Additional options include app-store (deprecated: use app-store-connect), ad-hoc (deprecated: use release-testing), and development (deprecated: use debugging).

so maybe you're running an older Xcode and we need to support both options?

[lucasfernog]

we should follow this approach and check the xcode version: https://github.com/flutter/flutter/pull/150407/files#diff-3596e48384307eec1b7905c5b22e524a9f7f9f1b6439e6ecfa2257fb1f2e8c28R584

[lucasfernog]

@jmilesj i just pushed a change, can you verify it still works for you?

[jmilesj]

@lucasfernog yes, you are right. The issue was with XCode 15.2.

I have tested your updates with both 15.2 and 16.2, they work smoothly!

Very appreciated we got both options available here! 👍

[lucasfernog]

sorry I forgot to follow up, forgot about this and ended up reimplementing it: #14106
thanks for your contribution though, I hope I don't lose sight of a PR like this again.