Create implied dependency on dedupe target when sorting

As discussed in #38.

This ensures that dedupe targets will be processed *after* dependencies that point to them.

I restructured the test case to fake this scenario and I'm open to suggestions on better ways to solve this. This solution has the advantage of working with the existing deps-topo-sort (and it cleans up after itself immediately), but it's kind of hacky.