Update bootstrap root keys

Johan Tibell is not part of the signing process anymore, so his key is
removed.

I've also annotated the keys with their owners and public keys,
because every time we consult this, I end up spending a bunch of time
in a scratch buffer correlating key IDs, public key values, and
ownership attestations. Might as well save the work for next time,
with appropriate disclaimers added.

Ensure js-sources are used only with JavaScript arch

* check: Test only doc files with supported extensions

* Cleanup

---------

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

* Fix repl discarding `build-depends` argument

Previously the function `\f -> L.allCondTrees $ traverseCondTreeC f` was
used to add the dependencies, but manipulating `CondTree` this way does
not update the nested fields `targetBuildDepends` of the tree, only the
conditions. It worked merely by chance if one does not further process
these fields: this explains why options like `--allow-newer` or
`allow-older` were incompatible with `--build-depends`.

Using `L.traverseBuildInfos . L.targetBuildDepends` ensures
`targetBuildDepends` fields and conditions are all updated consistently.

* Add test

* Add changelog

* Cleanup

---------

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Document the `remote-repo-cache` option as is implemented (it is).

For ghc calls pass Cabal's build/ directory after user's src/ directory so that contents of src/ takes precedence (#8690)

* Add test

* Pass build/ directory after src/ so that whatever’s in src/ will override any files we autogenerated

* Add expected output. Constrait test to run on recent enough ghc that will have Cabal updated

* Force test to requre development version of Cabal

Otherwise output will not be correct. It’s tricky to pass proper
Cabal/ version to this test because it needs it for the custom setup.

* Add changelog

* Fix other tests

Work around ghcup cache woes also in our dogfooding CI scripts

* Try to fix ghcup cache in CI via sudo chmod

* Revert "Try to fix ghcup cache in CI via sudo chmod"

This reverts commit 0bb71d10fa763b2f8f3382885d635ad1cfa09752.

* Try not caching store in validate jobs to avoid double package bugs

* Revert "Try not caching store in validate jobs to avoid double package bugs"

This reverts commit b3f378222886ddd754ccccc2a79fa500b78f4998.

* Try not to cache store on Windows in validate jobs

to avoid double directory package bugs.

* Revert "Revert "Try to fix ghcup cache in CI via sudo chmod""

This reverts commit b3a843a861cbddbe8ae9d44b20250d806f331cd3.

* Try sudo only on (new) Linux, where it should be available

* Also change the user

* Document the particular hack snippets in validate.yml

* Add an extra diagnostic ls for ghcup dirs

* Also hack the other affected CI scripts

* Also print the version of ghcup used for debugging

testuite: doctest: move to ghcup-recommended ghc

* Fix cabal init should not suggest Cabal < 2.0

* Remove + symbol cabal-version 2.0

elim warning spam from #8500

* Fix cli list parse errors in `cabal init`

Occurrences of `Flag [a]` behave in a slightly unexpected way. The monoid
instance of `Flag` is right associative and discard the value on the
left.
Thus, make sure we merge the contents of the flags, instead of using the
monoid instance of `Flag` itself.

* Document fixes and improvements

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

* cabal check: Warn if expected files are omitted from extra-doc-files

* Add test

* Add missing files and their hackage’s reference

* Move doc file check from checkPackageContent to checkPackageFilesPreDistribution

* Check based on globs only

Check only globs, not the filesystem.

* Update test outputs

* Make check more robust to relative paths

* Fix tests failing with "Distribution quality warnings"

* Fix comments and changelog [skip ci]

* Test changelog only if present

* Revert "Update test outputs"

This reverts commit ce49487d804691f77aff38b89449c2d0f09dbd44.

* Revert "Fix tests failing with "Distribution quality warnings""

This reverts commit 705f6bd0144057f5c1d375f9eceb90645b218a88.

* Fix changelog

* Remove getGlobFiles

* Adapt warnings to version 1.12

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Fix #8664 redux: add EOL character to list-bin output

* Add support for js-sources

* Add changelog

* Add comment about C-like sources

* Add tests

* Fix test

* Fix skipUnless and factorize

* Fix skipIfGhcVersion

Bump known ghc versions in cabal library to < 9.8

* Remove unused binding

* Add failing test

* Resolve import from relative paths within cabal.project

* Add expected test output

* Add changelog

* Remove unused imports

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Fix build instructions in CONTRIBUTING.md for people with old cabal

Add support for the -fprof-late flag new in 9.4

TargetSelector: Include a hint in the error message for internal error

This is a mediocre solution, and really should generate a different
error entirely at an earlier stage, but I'm not familiar enough with how
to achieve that.

* Add check for recursive glob in root directory

Such globs might be expensive to include, as they might pull unnecessary
 directories just like `.git` or `dist-newstyle`.

* Move expensive glob warning to its own constructor

* Add changelog entry

* Add test for recursive glob warning

* Fix formatting

cabal-testsuite #8401: communicate better the need for `--with-cabal`

- Add caveat to `--help` text.
- Put `--with-cabal` into very first example in README.

Rather than obfuscating by sprinkling in a fully qualified reference
to `<>` when unqualified references also work, limit the import of
`Data.Monoid.<>` with a suitable CPP.