Resolves #6209

Short description 📝

Users reported getting "static side effects" warnings that seem to be false positives in their projects. They happen when the project has Swift Macros; our logic doesn't account for that. We need to adjust the logic that checks for side effects to skip the traversal when it comes across a macro executable.

How to test the changes locally 🧐

Create a project with an app that depends on 2 dynamic frameworks
Add a Swift Macros to each of those 2 dynamic frameworks
Generate the project

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