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.
Two things:

1) ``SHOW_CUSTOM_BADGE_INPUT`` is a Python boolean, so if you just render it into your Javascript code like this, it'll render as ``True`` whereas Javascript expects boolean true to be the lowercase ``true``.  So I'd expect this to give a Javascript error.  I'd recommend saying ``{{ SHOW_CUSTOM_BADGE_INPUT|jsonify }}`` to convert it properly.  Is this not giving you a Javascript error?  I'm kind of surprised and we should run this to ground before merging.

2) As a minor stylistic matter, I'd not bother with the local variable if it's only used on the very next line and then never again.  I'd just say  ``if ({{ SHOW_CUSTOM_BADGE_INPUT|jsonify }}) {``