Fix Swift Macros unresolved by the Xcode editor

[pepicrft]

Short description 📝

Under some scenarios, for example when not using conventionally-named configurations, the Xcode editor failed to recognize the Swift Macros, even if the build system compiled them successfully. To fix it, I replaced the $BUILT_PRODUCTS_DIR, which is the directory where we copy the Swift Macros executables into, by $(BUILD_DIR)/$(CONFIGURATION), which represents the source macOS directory where executables are output by default.

I tested the changes with a project that contains Macros and configurations other than Debug and Release and the editor is able to resolve them successfully.

How to test the changes locally 🧐

You can take a project with Swift Macros, for example fixtures/framework_with_native_swift_macro, change the configuration names, and try to edit the Framework.swift.

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]

Great find 👏