Tuist shouldn't generate empty Embed Precompiled Frameworks and Embed Frameworks build phases

[natanrolnik]

Describe the bug

When creating a project with a target without any build phases (TargetActions), two empty build phases are added, unnecessarily: Embed Precompiled Frameworks (runScript) and Embed Frameworks (copyFiles).

To Reproduce

1. Create a Target without specifying any TargetActions
2. Add this Target as part of the declared Project.
3. Check that two empty build phases are added: Embed Precompiled Frameworks (runScript) and Embed Frameworks (copyFiles).

Expected behavior
If there are no precompiled or embedded frameworks, do not generate these empty build phases.

Screenshots
When comparing the diff with an existing project via xcdiff, the following is shown:

Desktop:

• macOS 10.15.3

Additional context

This was discussed in the public Tuist slack channel. Thanks to @kwridan for taking a look into it and suggesting. Although it's not a bug, it's definitely something that can be enhanced.

[kwridan]

Thanks for raising this @natanrolnik 👍

Having them there as empty build phases shouldn't be harmful. If you're interested in tackling this - the class responsible for adding those particular build phases is LinkGenerator

The thing that is worth checking is if any of the acceptance tests validate those empty build phases, they would potentially need to updated to perform a different check if we remove those phases completely.