Disable per-component build when program coverage enabled

Creating the test program coverage report requires the test runner to know the
build directory for the library component. If per-component builds are enabled,
this is not possible because the library is not in-scope at the same time as the
test component. The only apparent solution that does not require rethinking
per-component builds entirely is to disable it when coverage is enabled.

Resolves: #4798

Author: ttuegel

cabal-install/Distribution/Client/ProjectPlanning.hs

@@ -1211,7 +1211,7 @@ elaborateInstallPlan verbosity platform compiler compilerprogdb pkgConfigDB
       where
         -- You are eligible to per-component build if this list is empty
         why_not_per_component g
-            = cuz_custom ++ cuz_spec ++ cuz_length ++ cuz_flag
+            = cuz_custom ++ cuz_spec ++ cuz_length ++ cuz_flag ++ cuz_coverage
           where
             cuz reason = [text reason]
             -- At this point in time, only non-Custom setup scripts
@@ -1243,6 +1243,12 @@ elaborateInstallPlan verbosity platform compiler compilerprogdb pkgConfigDB
                 | fromFlagOrDefault True (projectConfigPerComponent sharedPackageConfig)
                 = []
                 | otherwise = cuz "you passed --disable-per-component"
+            -- Enabling program coverage introduces odd runtime dependencies
+            -- between components.
+            cuz_coverage
+                | fromFlagOrDefault False (packageConfigCoverage localPackagesConfig)
+                = cuz "program coverage is enabled"
+                | otherwise = []
 
         -- | Sometimes a package may make use of features which are only
         -- supported in per-package mode.  If this is the case, we should