Check .may_include order and tor subsystem init order are compatible
In legacy/trac#31615 (moved), we discovered that our module init order doesn't match their dependency order.
Let's use practracker and tor to make sure that doesn't happen again. We'll probably need a new make check target, because we'll need a compiled tor and practracker output. See legacy/trac#31615 (moved) for details.
Gaba, this is Sponsor 31-can, because it helps us catch refactoring bugs when we create new modules.
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information