Do not generate resource accessors for internal targets with resources and Objective-C source files

[fortmarek]

Short description 📝

As reported by Etsy, their GCC_PREFIX_HEADER is unexpectedly overridden by tuist. This regression was introduced here. At the time, we thought overriding GCC_PREFIX_HEADER should be fine but this assumption turned out not to be true.

For the time being, we will again no longer generate objc resource accessors. We can start generating them again once we figure out how not to use GCC_PREFIX_HEADER as described here.

How to test the changes locally 🧐

An internal target with objc files and resources shouldn't have tuist-generated resource accessors.

Contributor checklist ✅

• The code has been linted using run mise run lint:fix
• The change is tested via unit testing or acceptance testing, or both
• The title of the PR is formulated in a way that is usable as a changelog entry
• In case the PR introduces changes that affect users, the documentation has been updated

Reviewer checklist ✅

• The code architecture and patterns are consistent with the rest of the codebase
• Reviewer has checked that, if needed, the PR includes the label changelog:added, changelog:fixed, or changelog:changed, and the title is usable as a changelog entry

[darrarski]

This is great! I experienced the problem yesterday, and I was about to open an issue. Thanks for your valuable contribution! ♥️