Warmed cache binaries are now reused by generate and build

Targets warmed with tuist cache warm <target> were sometimes silently rebuilt instead of reused by tuist generate --cache-profile all-possible and by build/generate cache replacement, because warm and consume computed different cache keys for the same target. This release aligns the cache hashing graph between the warm, generate, and build flows, so a warmed binary is now actually reused and linked when the target’s logical inputs have not changed (for example, a dynamic framework wrapping external precompiled dependencies).