Cache warm hashes now match generation, so warmed binaries are reused instead of rebuilt

Targets warmed with tuist cache warm are now correctly reused by tuist generate --cache-profile all-possible and by build/generate cache replacement paths when their logical inputs are unchanged. Previously the warm step hashed a normalized graph that the unfocused generate/build binary-replacement step did not, so warmed wrappers of precompiled dependencies were silently rebuilt even though the project itself had not changed.