Checkpoint: dependendency ordering.

It's still not working correctly...
ConfigFlattener works.

- Fixed dyslexic definition of dependent and dependee.
- Any newly-generated configs need to be further processed.
Added ConfigToolUtil to hack around protected access.

It was either this, make the method public, move the
flattener out of tools, or use reflection.
Attemp to generate stable names for flattened configs.
Checkpoint...

Now I'm trying this on a much larger dataset (SK's entire config set)
and it's running into problems with dependencies when it adds a new
config that depends on a config that's already been processed.
Ugh.