Add buildArchitectures to XCScheme+BuildAction

[woin2ee]

This PR is related to tuist/tuist#6003

Short description 📝

It makes enable to set Override Architectures option of build action.

Solution 📦

I observed the changes in the xcscheme file as I changed the Override Architectures option. After that, I decided to add the attribute in a similar way to the existing implementation of buildImplicitDependencies and runPostActionsOnFailure.

Implementation 👩‍💻👨‍💻

• Add an enum to represent the Override Architectures option.
• Add buildArchitectures property in XCScheme.BuildAction.
• Add and Update tests

[kwridan]

nice work @woin2ee - thanks for contributing this

[kwridan]

From testing in a Xcode, unspecified or random values default to useTargetSettings

Suggested change

	self = .matchRunDestination
	self = .useTargetSettings

Alternatively can make this an failable init (init?)

[woin2ee]

That's right. It’s my mistake. 🙏

[kwridan]

This is an interesting one

• New schemes created in the Xcode UI do indeed default to .matchRunDestination
• The current released version of XcodeProj doesn't explicitly write this attribute when creating new schemes (i.e. would be .useTargetSettings)

Having matchRunDestination as the new default for the init here would introduce a change in behaviour for existing clients of the library and all their generated schemes would go from .useTargetSettings > .matchRunDestination 🙈

Suggested change

	buildArchitectures: Architectures = .matchRunDestination) {
	buildArchitectures: Architectures = .useTargetSettings) {

[woin2ee]

The current released version didn't have control over this attribute, so I thought it wouldn't affect existing clients as if it were a new feature.
However, I missed the fact that there may be clients who are using the current version's settings well. Thank you for your review.

[kwridan]

Thanks for the updates @woin2ee

[kwridan]

@all-contributors add @woin2ee for code

[allcontributors]

@kwridan

I've put up a pull request to add @woin2ee! 🎉