There are several places in the codebase where we use SCons generators with meaningful for_signature handling to ensure that changes to certain sorts of files (e.g. sanitizer suppression lists or symbol export lists) cause rebuilds. We are sort of cheating though, since what we are changing with those generators is the build signature of the target, and not properly introducing a real implicit dependency.

While implementing support for forced includes in SERVER-55833, we learned of some of the downsides of this approach, and that we should instead be making proper use of Scanners to achieve this effect.

Revisit our signature based injections and figure out how to use Scanners for those purposes instead.