RFC: dense blkdiag

I needed this earlier this week. This is a truly naive approach, and I'm sure it can be improved, but it does seem to get the job done.

cf. #5828
Because both the sparse and dense versions are defined with a single `...` argument, you get an ambiguity warning if you don't define the zero-argument version. Alternatives?