Superformat

This is a significant refactoring of view handling to make formats/views work much more like cards/events.

Until now the primary mechanism for handling sets in formats has been special method naming for views.  Now views (and other format methods) are handling by module inclusion at initialization time.

The main difference is that there are multiple format classes involved, so there are potentially multiple format modules per set.  For example, for Pointer+*type, you would have just the one "set module"

Card::Set::Type::Pointer

..but you could have many "set format modules":

Card::Set::Type::Pointer::Format
Card::Set::Type::Pointer::HtmlFormat
Card::Set::Type::Pointer::CssFormat
...

and those would need to get included in the right contexts (as they now do).

This pull request is NOT yet ready for merging.  There are still a few specs failing (7 I think), mostly because I haven't yet worked out a good mechanism for sharing view handling among different sets.  Eg many things in the file set formats need to be used in image set formats, cards with the type Set inherit functionality from cards with the type Search, etc.

haha!! yeah, I would never do it all just for "super".

There was an accumulation of lots of cases where we kept needing set-specific format methods, so we kept artificially sticking things in views just to have some sort of mechanism.  Meanwhile we kept sticking stuff in the base format classes that really didn't belong there.

I typically only take this kind of thing on if I've felt the frustration behind it lots of times, and this one definitely qualifies.  The wikirate work demands a lot of set-specific format behavior, and every solution was feeling hacky without this.  This new handling makes the API feel much more complete and harmonious.  Cards and Formats basically work the same way.