Fix integration of SPM dependencies with resources

[fortmarek]

Resolves #3785

Short description 📝

Based on an original attempt at fixing this: #4902

This PR synthesizes the SWIFTPM_MODULE_BUNDLE for Objc external targets.

We use the fork of NYTPhotoViewer not because the accessors are wrong, but they have two targets that point to the same directory, one using a symlink. We then generate two different modulemaps pointing technically to the same dir. I believe this is currently not worth solving unless we find more dependencies this imho awkward setup.

How to test the changes locally 🧐

You should be able to build app_with_spm_dependencies fixture.

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

[fortmarek]

This solution is not ideal as we're overriding this setting: #4902 (comment)

However, this setting is not really used by SPM targets (I couldn't find any that would and it's generally discouraged to use this setting unless for very special purpose) and we don't apply this for internal targets. If this becomes an issue, we can rethink this. I did try using the -include C flag but that caused issues due to import of Foundation and I haven't explored this further.