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.

Not so much confused is that I thought the resolving done there could interfere with this, maybe it doesn't.

We used: define_method new_name, &block
which is probably what alias does internally (in effect anyway).
If I get your solution, it is similar to what I was thinking.  You just have to be able to find the referent block (lambda), and I can see how "a bit more mapping" at load time could do it.  It should work for the case you handle too, right?  If we can resolve it to a block in the complex case, the simple one should work that way too (no send).