0538d565

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

Remove stack support in favour of cabal

We build with cabal now, so stack.yaml was a second, redundant
description of the project: its extra-deps duplicated flake.nix's inputs
(which are a superset of them), and the nix devShell already supplies
those dependencies, so cabal needs no source-repository-package stanzas
to resolve the project.

stack.yaml was, however, the only thing applying the warning set to
development builds. nix/overrides.nix applies the same list plus -Werror,
but only to nix builds, so deleting stack.yaml on its own would have
quietly left plain cabal builds with GHC's defaults. Move the list into
each package.yaml instead, where it reaches every component and every
build path. The tradeoff is that these flags now ship in the .cabal
files.

Drop the now-dead .stack-work and *.yaml.lock ignores while we are here.

Timeline