Support passing xcodebuild arguments to build and test

[pepicrft]

Context

When we implemented the commands tuist test and tuist test, we thought it'd be a good idea to completely abstract away the invocation of xcodebuild, which we use internally for building and running the tests. The role of tuist test and tuist build would be:

1. Providing developers an easy way to prettify the raw xcodebuild logs
2. Collecting and pushing metrics from test runs and builds to build analytics upon
3. Enhancing the interface of the xcodebuild CLI aligning it with industry conventions, improving the descriptions, and enhancing the help menus and the visual hierarchy that's presented in them.

While 1. and 2. were good ideas, 3. turned out to be bad because it requires adding support for every xcodebuild argument that developers want to use.

What

I suggest that we take steps backs to:

1. Remove from tuist build and tuist test arguments and flags that are already accepted by xcodebuild
2. Support forwarding arguments and flags directly to the internal xcodebuild process.

For each command, tuist build, and tuist test, we'd need to:

1. Mark all the flags and arguments that are already accepted by xcodebuild as deprecated (e.g. --os, --rosetta and --device in favor of xcodebuild's -destination flag)
2. Capture non-Tuist arguments in an array of strings that we'd then forward to the xcodebuild process.

[!IMPORTANT] Deprecations
Note that we can't remove existing flags because that'd be a breaking change for projects whose automation might already be using those flags and arguments. I'd extend the description of those to mention that they are deprecated, and also show a warning using WarningController if we detect that developers are using them.