Cache warm and generate keys are aligned

Targets warmed with tuist cache warm <target> are now reliably reused by tuist generate --cache-profile all-possible and by build/generate binary cache replacement paths. Previously, the warm and consume paths could compute different cache keys for the same logical input (notably frameworks wrapping precompiled dependencies), causing silently rebuilt binaries on the consume side.