Support module thinning and renaming Cabal-side.

NB: unlike GHC, Cabal will still try to find a globally consistent choice for
all package names, i.e. this does *not* implement private dependencies.

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>
Given the comments, this might be clearer as a record with descriptive names for the two fields. Something like `moduleRenamingIncludeOriginals` and `moduleRenamings`?