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.
I would like to have the documentation of the number of universe parameter next to the definition of the function (since the latter also documents the non-universe parameters).  Are you saying that the `Check` here should be commented out, or replaced with a comment, and then added uncommented to the `Tests.v` file?  Do you want to avoid `Check` in files other than `Tests` only because it prints something to the console when run with coqtop?