Improve hunt configuration experience

[dlareau]

This takes the form of 3 improvements (as of writing)

1. Fix the config syntax hacks we've discovered. As of right now this is mainly allowing a more direct "time after" statement to prevent lines like "Y <= every M after X solve limit 1"
2. Make it easier to think about puzzle IDs when editing the config. I think the most realistic option I have at the moment to ease this is being able to specify ID or order number. Something that would be nice to verify the config is the config with each ID replaced with the puzzle name. I don't think being able to specify by name is reasonable, but verifying sounds good.
3. Add some sort of configuration tester page. This likely would just be a tab on the configuration page, but the idea is to be able to test configurations without having to make a playtest team. This should ideally have a column of togglable buttons to say if a puzzle has been solved or not, a column of indicators showing which puzzles are unlocked, and a few buttons to do things like set what time it is. The only thing that simple interface doesn't easily allow is noting exactly when a puzzle was solved for time based unlocks, but maybe that could be solved with a little time edit widget underneath each button.

[dlareau]

Another syntax to add to prevent hacks is some way of saying "solving these puzzles give N points each" to avoid having a dozen N POINTS <= PXXXXXX statements.

[dlareau]

This is now being worked on in issue #35

[dlareau]

Fixed in #35