Unconditionally turn on package name munging for components.
A lot of tooling (Cabal's included) assumes that if something in the installed package database has 'name: foo', it is a valid choice if we are dependency solving for 'foo'. If we always name internal libraries something else, this tooling will not get confused. So let's help them out. Signed-off-by: Edward Z. Yang <firstname.lastname@example.org>