Separate product and sum into own modules

[rossabaker]

Large modules, such as Network.AWS.ECS.Types, take too long to compile. This generates each generated sum and product into their own module, which are then re-exported in Types. There are two advantages:

1. Smaller modules promote parallel compilation, so wall time drops.
2. Compilation of large modules is superlinear, so total CPU time drops.

This change should be compatible.

[brendanhay]

I have various branches and code lying around that benchmarked a couple of different type module layout algorithms specifically designed to optimise compile time. Somewhat hilariously, I never tried one type per module! 😆

From what I vaguely remember of the experiment results, the optimal solution was to use Data.Graph.stronglyConnComp in conjunction with some form of bin packing to create 'fairly smol modules, but not too smol' according to an adjustable threshold.

Love this change, straight forward and simple.

[rossabaker]

I wouldn't be surprised if bin packing improved it further. Also wouldn't be suprised if the optimal bins depended on the cores. The important thing is that this splits up the EC2.Types monstrosity. 😄