20a687b8

By: Tom Sydney Kerckhove <syd@cs-syd.eu>

Cover the GADT and multi-selector paths of the prefix rule

A constructor written in GADT syntax, a record field written there, and one
field declaration naming two selectors each reach code the resources did not
exercise.

Dropped ScopedTypeVariables with them: the annotation on the listify
predicate binds no type variable, so the extension was never load-bearing.
e2e-added-rule-is-rune2e-artifacts-are-reade2e-choices-are-found-beside-the-repositorye2e-cleane2e-dirty-package-is-judged-failinge2e-dirty-project-is-judged-failinge2e-dirty-report-is-readablee2e-disabled-rule-is-not-rune2e-incomplete-artifacts-are-a-failuree2e-judging-nothing-failse2e-named-packages-are-every-packagee2e-no-packages-is-judged-failinge2e-no-store-paths-in-findingse2e-paths-are-repository-relativee2e-withheld-facts-faile2e-wrong-source-mapping-is-a-complainthlint-checkhopinionpre-commitreleaseshellweeder-checkconfiguredevShelldefaultx86_64-linux