Share cache entries even if -Cprefer-dynamic and -Cextra-filename differ
          #2469
        
          
      
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Makes two changes that improve the cache hit rate if switching between compilation with
-Cprefer-dynamicand not. First, because sccache only cachesrlib/staticlibcrates,-Cprefer-dynamichas no effect and can be ignored (it is often set via globalRUSTFLAGS).Similarly, the Cargo-generated fingerprint is easily invalidated by custom
RUSTFLAGS, but since sccache has fine-grained knowledge of therustcinvocation it should ignore this fingerprint. We do this by ignoring this flag in the cache key, and also stripping the-Cextra-filename(which Cargo uses to append the fingerprint to outputs) from the keys of the output files.Most of this behavior is (to my understanding) covered by the existing tests, but I adjusted a hashing test to ensure these two flags are correctly ignored.