Cache warm and cache reuse share the same hashing graph, so warmed binaries stop being silently rebuilt

Targets warmed with tuist cache warm <target> are now correctly reused by tuist generate --cache-profile all-possible and by build/generate cache replacement paths when their logical inputs are unchanged. Builds/generate had been hashing the graph before the same FrameworkSearchPathsGraphMapper normalization that warm applies, so warmed binaries were silently rebuilt. The hashing graph is now preserved across all binary cache paths.