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.



probably a little performance, yeah.  There's kind of a lot of questions about the API from my perspective:

1. do we like the word "render" (I think no)
2. do we really want to make skipping permissions so easy/standard with the underscore (I think no again; not sure it's necessary now that we're caching perm checks)
3. should render_myview be as standard as render :myview (no again for me)

I suspect as we resolve those we'll want to optimize a good bit more.  My main objective with this implementation was just to get it working.  The upside is that it's much simpler.  I think it's good to start with simple and then use a profiler to optimize to make sure you're addressing actual problems.