Cache warm hashes align with generation, so warmed binaries get reused

A target warmed by tuist cache warm is now reliably reused by tuist generate –cache-profile all-possible and by build-time cache replacement. Previously, framework search path setup was part of the warm-side hash but not part of the consume-side graph before binary replacement, so warmed artifacts were silently rebuilt for any wrapper dynamic framework. The mapper factory now preserves a normalized hashing graph for build/generate flows, so warm and consume paths derive cache keys from the same state.