Match cache warm hashes with binary cache reuse

After the rc.1 regression where cache warm stored a target under a different cache key than the one requested by tuist generate --cache-profile all-possible, the binary replacement step now preserves the same normalized hashing graph (after FrameworkSearchPathsGraphMapper) that cache warm uses. Warm and consume cache keys stay aligned so all-possible reuse returns the warmed binary for frameworks that wrap precompiled dependencies instead of rebuilding from source.