cabal-install 3.14.1.1 release notes

Add `make style-todo` and fourmolu on off comments

Only munge internal dependencies when printing when there is no explicit syntax

* In `postProcessInternalDeps` the shadowing logic which existed prior
  to cabal format 3.4 is implemented in a post processing step.

  The algorithm there replaces any references to internal sublibraries
  with an explicit qualifier. For example if you write..

  ```
  library
    build-depends: foo

  library foo
    ...
  ```

  this is reinterpreted as

  ```
  library
    build-depends: mylib:foo

  library foo
    ...
  ```

* In `preProcessInternalDeps` the inverse transformation takes place,
  the goal is to replace `mylib:foo` with just `foo`.

* Things go wrong if you are using version 3.0 for your cabal file
  because
  - In 3.0 the qualifier syntax is introduced so you can be expliciit
    about sublibrary dependencies
  - The shadowing semantics of non-qualified dependencies still exists.

  So the situation is that the user is explicit about the sublibrary

  ```
  library

  library qux
    build-depends: mylib:{mylib, foo}

  library foo
  ```

  1. Post-process leaves this alone, the user is already explicit about
     depending on a sublibrary.
  2. Pre-processing then rewrites `mylib:{mylib, foo}` into two
     dependencies, `mylib` and `foo` (no qualifier).
  3. When parsed these are two separate dependencies rather than treated
     as one dependency, roundtrip test fails.

Solution: Only perform the reverse transformation when the cabal library
version is <= 3.0 and doesn't support the explicit syntax.

Now what happens in these two situations:

1. ```
   library
     build-depends: foo

   library foo
     ...
   ```

  this is reinterpreted as

  ```
  library
    build-depends: mylib:foo

  library foo
    ...
  ```

  then printed and parsed exactly the same way.

2. Explicit syntax is parsed and printed without being munged (when
   supported)

Note: Mixins only supported sublibrary qualifiers from 3.4 whilst
dependencies supported this from 3.0, hence the lack of guard on the
mixins case.

Fixes #10283

make formatting of `build-depends` consistent

https://github.com/haskell/cabal/pull/10714/commits/7d791b9da10b5034e7a997a0044ded5575fe123f

`*.cabal` files in this project presently have a mix of formatting of `build-depends`.
Make them all consistent with:
https://cabal.readthedocs.io/en/3.4/cabal-package.html

No changes to any dependencies.

Add a cabal target command

Fix file+noindex URI usage on Windows

Fix #9507 Describe accurately acceptable package names

Also extinguishes false positive in typo detection.

Also aims to make corresponding changes to buildinfo-reference-generator, including the `Cabal-described` package. Adds `alphanumNotDigit` and now specifies `alphanum` by inserting digits into `alphanumNotDigit`.

The description of `alpha-num-not-digit` is added to the introduction to the section on 'Non-terminals' to accommodate the limitation of buildinfo-reference-generator that only a single 'formula' can follow a single paragraph of narrative for each non-terminal production.

cabal-install.cabal: bump upper bound for random

Add support for Windows Aarch64

Co-authored-by: Cheng Shao <terrorjack@type.dance>

- Avoid list in the help
- Use establishProjectBaseContext
- Remove withContextAndSelectors
- Use rebuildInstallPlan and resolveTargets
- Extract targetForms
- Satisfy hlint
- Remove unnecessary do
- Use safeHead
- Call printPlanTargetForms for everything
- Remove planTargetForms
- Rework command description
- Remove script as a possible TARGET form
- Section help into; intro, targetFroms and ctypes
- Use pretty printing for examples
- Short form and long form
- Add a changelog entry
- Need nixStyleOptions for cabal-testsuite
  - unrecognized 'v2-target' option `-vverbose +markoutput +nowrap'
  - unrecognized 'v2-target' option `--builddir'
  - unrecognized 'v2-target' option `-j1'
- Use notice so target forms are marked output
- Add tests of target all, implicit and explicit
- Add tests of all:exes and all:tests
- Add test of all:benches
- Add tests with --enable-tests and --enable-benchmarks
- Warn that package targets display libs and exes
- Add package target tests
- Add path target tests
- Add component target tests
- Add c package with only a library
- Add tests for missing ctypes
- Exclude new-target from other commands
- Move target command to configuration group
- Add target command docs
- Add cabal target docs
- A significant change
- Drop cleans from tests
- Use noticeDoc to preserve indent
- Satisfy fourmolu
- Show the number of matches found matching query
- Change synopsis of command, target verb
- Remove disclosed, use show, WARN and NOTE
- Typo command singular
- Bring the command docs inline with --help docs
- Remove disclosing from changelog
- Only by default, not *only*.

Co-Authored-By: brandon s allbery kf8nh <allbery.b@gmail.com>

Remove unused -XCPP

Fix file+noindex URI usage on Windows

Cabal: Honour -working-dir flag when running test executables

A simple fix to run the test executable in the `-working-dir`.

Fixes #10704

Suppress ghc-pkg warnings emitted when an empty packages is being registered

When a package contains a library that has no modules, "./Setup register"
tries to register the library with fields "haddock-interfaces:" and
"haddock-html:" pointing at non-existent files or directories, and "ghc-pkg
register" warns about them.

To suppress the warnings prevent these fields from being generated when
there are no modules.

Ignore haddocks

- Remove redundant -XCPP from Cabal-tree-diff
- Remove redundant -XCPP from cabal-install
- Remove redundant -XCPP from Cabal
- Remove redundant -XCPP from Cabal-QuickCheck
- Remove redundant -XCPP from Cabal-syntax
- Remove redundant -XCPP from Cabal-tests
- Remove redundant -XCPP from cabal-testsuite

Follow HLint suggestion: use fewer imports