(6911) Core change -- replace topsort with frontier ordered by salted SHA1

This is the core change of the ticket; rather than using a topological sort to statically
determine the order in which resources should be applied, we use the graph wrapper
introduced in the prior commit to dynamically determine the order in which to apply
resources based on 1) the status of the resource (ready, done) 2) the explicit &
implied dependencies, 3) the salted SHA1 of the title (for stability).

Further work is needed:

1. Resolving the handling of failed resources
2. Tests of the new behavior, to the extent posible
3. Newly-dead-code removal in simple_graph & transaction
4. Fix the name-prefix ordering hack in eval_generate by either: a) Moving the logic into file b) Refactoring Type#eval_generate to return a tree c) ....?
5. Rough performace testing to look for hotspots
6. Investigation of possible interaction with #3788, #5351, #5414, #5876, #6020, #6810, and #6944 which may simplify or complicate their resolution.

Paired-with: Jesse Wolfe