Cached frameworks no longer embed external SwiftPM resource bundles

tuist cache warm no longer substitutes cached external resource bundle artifacts into internal source frameworks. Transitive SwiftPM resource bundles are now kept as source dependencies when the receiving target is a framework, so they embed once at the app level instead of being copied into every internal framework that depends on the package. Frameworks shrink back to their actual contents and the resulting app bundle no longer carries the duplicated resource bundles.