Use modules for reflective subuniverses and modalities

This is option (4) at #596.  It's still a bit annoying, but I think it's made manageable by the technique of making the module types represent a _family_ of subuniverses or modalities.  The universe polymorphism is fiddly when defining particular examples, but once they are defined, it's basically invisible, which is how it should be.  Note that hardly any of the substantial code has to be modified; most of the changes are in the boilerplate.  There are a couple of minor anomalies that have to be worked around (still working on bug reports), but nothing too major.  Right now I think this is probably the way to go -- I don't even know how to do option (3) for lex modalities -- but I'd be interested in what others think.  I'm also very open to feedback on the best way to name and manage the modules; I proposed one possible convention, but I don't know that it's the best.
A path is something like `foo.bar.baz` (what I'm calling a "kernel name" above).  `Accessible_ReflectiveSubuniverses` is a "module" (functor), and you're applying it to `Modalities_to_ReflectiveSubuniverses Os`, which is not a path, but instead an application itself.

If you have a suggestion of a better error message, you should probably make a request on the bug tracker.