Rockage

code changes needed for Rockage

everything here -I think- is totally compatible with m13's uber, however, there are some config settings that have been removed that we will need to make sure get put back in place via puppet

this is now ready for a real code review @EliAndrewC.  The point of this code review is to make sure that none of the changes in here are rockage-specific and would break m13 uber.  All of the rockage-specific bits are in their own rockage sideboard plugin.

Since Rockage doesn't have actual badges, or sells tshirts, this adds a bunch of config settings that control which parts of the prereg forms are shown/hidden including:
- whether we ask attendees for their names to print on supporter badges
- whether we ask attendees their shirt sizes, or require it when reg'ing a supporter

This also breaks out a few more sections of the prereg code into their own template files, which get overridden by the rockage plugin.  This allows us to change a lot of text for confirmation emails/etc.

Huh. On actually doing this code review, there's a hell of a lot less changed in this project than I thought.  Pretty cool.
I completely agree that the actual production values belong in puppet and not in the core repo.

With that being said, it's often useful to keep some value in the core repo even if it's not the actual production value.

What I'll probably do next year is this:
- ``configspec.ini`` will continue to have the sorts of things it has now
- ``development.ini`` will continue to just not exist in the repo so that we can use it for local overrides
- ``development-defaults.ini`` will have some settings enabled by default for testing, and have some other commented-out settings with comments that basically say "here's what you should put in your local development.ini if you want to set the deadline for customized badges on your dev server