Resolves #7515

Short description 📝

When a transitive dependency is referenced with the registry identifier in the Package.swift without the --replace-scm-with-registry flag being used, SwiftPM ends up resolving both the scm and registry variant of the dependency. Tuist then ends up "randomly" using one or the other.

This PR fixes the issue by preferring a registry dependency if available. However, we recommend using --replace-scm-with-registry as a dependency resolved twice with possibly different versions is rarely what you want.

How to test the changes locally 🧐

• See the attached issue.

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