Define Archive Action on Scheme

[pepicrft]

Copied from #529

---

Short description 📝

The purpose of this PR is to add support for defining a custom archive action when defining a scheme, so that we're able to provide a configuration when running the archive job.

Solution 📦

The solution I propose is to follow the same implementation that is already being used on the other action's definitions.

Implementation 👩‍💻👨‍💻

• Create class ArchiveAction
• Add archiveAction attribute to Scheme class
• Implement method for generating a XCScheme.ArchiveAction from an ArchiveAction
• Implement unit tests
• Update documentation

[rowwingman]

Should I push my own pull request https://github.com/rowwingman/tuist/tree/archive-action to finish this one? Fixed errors with last two commits

[pepicrft]

What about pushing to this one directly? You should have received a GitHub invitation to be collaborator of the organization. Once you accept it you should be able to push directly to this branch.

[rowwingman]

@pepibumur can you review, and merge if everything is ok

[pepicrft]

@rowwingman the following acceptance tests broke with the changes in the PR:

Scenario: The project is an iOS application with watch app (ios_app_with_watchapp2)                       # features/generate.feature:233
    Given that tuist is available                                                                           # features/step_definitions/shared/tuist.rb:3
      swift build
    And I have a working directory                                                                          # features/step_definitions/shared/workspace.rb:6
    Then I copy the fixture ios_app_with_watchapp2 into the working directory                               # features/step_definitions/shared/fixtures.rb:5
    Then tuist generates the project                                                                        # features/step_definitions/shared/tuist.rb:7
      swift run tuist generate --path /var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/d20191124-1969-vtaw5t
    Then I should be able to build for watchOS the scheme App                                               # features/step_definitions/shared/xcode.rb:6
      xcodebuild -scheme App -workspace /var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/d20191124-1969-vtaw5t/App.xcworkspace -derivedDataPath /var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/d20191124-1969-vtaw5t/DerivedData clean build CODE_SIGNING_ALLOWED=NO CODE_SIGNING_IDENTITY="iPhone Developer"
      ** BUILD FAILED **

[adamkhazi]

This PR looks good to me. The acceptance test passed for me too locally. I will rebase and start submitting PRs related to #667 once this lands.

[rowwingman]

@pepibumur Looks fine after rebase