[WIP] Refactor Tourney classes

[isaacl]

• Move recently created complex logic into its own object
• Add a deterministic tourney stagger method
• Add stagger to Plan objects, rather than Tournaments to be more easily testable.

[isaacl]

This probably works, though I haven't tested. However it's kind of a hot mess of code. I'm struggling to figure out how to simplify. I don't really need a TreeSet for the tiny list of tourneys, but even without that structure, the code looks the same.

This whole change is probably overkill, but the idea was:

• clean up and segregate the logic I've been dumping into tourney classes
• uniform random staggers are not particularly good at their job -- they cause tourneys to be closer together than might be expected.

Still, it feels like a lot of verbose code for a relatively small issue :-\ so not sure what to do.

[ornicar]

It's a lot of tricky code to review. I did read it quickly and found nothing alarming. I deleted my local tournaments and let it re-create them. They look fine, and the deterministic stagger is certainly nice.

Surely there are some bugs lurking, and it's ok to find them later, in prod.

[isaacl]

I’ll be adding tests of the new code before it’s ready to land. Will follow up.