Fix runtime crash when using Obj-C dependencies

[fortmarek]

Short description 📝

As reported by @freak4pc, the current fix for ObjC dependencies is missing the addition of the -ObjC linker flag. When accessing ObjC code without this flag, the app crashes with an unrecognized selector sent to instance ....

We can add the flag whenever there's a modulemap as that's a good way to tell if a target has an objc dependency.

How to test the changes locally 🧐

Run app_with_spm_dependencies app. Before this PR and with the current changes in AppKit, the app would crash in runtime.

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

[freak4pc]

Amazing ❤️

[amarcadet]

I wonder if the same principle could be applied to add the -all_load flag as well. Some crashes could occur if objc packages contains categories. I had to do it to fix crashes with some Firebase related lib that has categories on NSData.

[freak4pc]

I think we need to be careful with auto-loading compiler flags onto the Xcode Projects unless they are an industry standard of obvious. Things like -all_load could be quite problematic and it's better to leave customized. I think it's good to think about it as - if Xcode does it automatically, Tuist probably should too (i.e. when you add ObjC - Xcode will automatically add that flag, bridging etc). Otherwise, it should be manually customized.