Rename projects to have `.project` extension

Correctly provision build tools in all situations

This patch ensures that we correctly provision executables declared
in the build-tool-depends fields in all circumstances:

  - whether the build tool is external (from another package) or
    internal (declared in the current package)
  - whether the build tool is used at compile time (e.g. in a pre-build
    rule or in a Template Haskell splice) or at run time (e.g. when
    running a test-suite, benchmark or executable).

Note that correctly provisioning a build tool requires two pieces of
information:

  - making it available in PATH,
  - ensuring it has the correct environment variables overrides;
    in particular, the build tool needs to be able to find its own
    data directory.

The test case BuildToolPaths checks all of these situations are handled
correctly.

This commit ensures the test-suite driver also provides the Cabal-hooks
package, on top of Cabal and Cabal-syntax.

Define a user-visible change

Update PR template

Stress an API change is enough to warrant a `changelog.d` entry.
Check #9856 to see why we need it.

Reinstate 'initialBuildSteps' function

This patch reinstates the 'initialBuildSteps' function, as it is
used by stack in its implementation of the multi-repl feature.

A deprecation warning has been added to that function: calling it does
not suffice to prepare the sources for a package, as there are other
steps that one might also need to perform:

  - running pre-processors (such as alex/happy)
  - running pre-build hooks or custom logic (in build-type: Hooks
    or build-type: Custom or Configure)

Consumers wanting to prepare the sources of a package, e.g. in order to
launch a REPL session, are advised to run
`Setup repl --repl-multi-file=<fn>` instead.

Fixes #9856

- Rename cabal.bootstrap.project
- Rename cabal.meta.project
- Rename cabal.validate-libonly.project
- Rename cabal.validate.project
- Rename cabal.release.project

State supported GHC versions in release notes

Add warning and note to cabal test [TARGETS]

CI: force MacOS jobs to use Intel runners (macos-13)

- Add anchor for user-visible change

GitHub just switched macos-latest to the ARM chips (now alisasing
`macos-14`), and it brings a bunch of problems.

- First of all, GHC's 8.8 and 8.6 don't exist there.
- ghcup and llvm are unavailable

For the time being, lets stay on the previous version of the runner.

* Add `initialBuildSteps` removal notice

And suggestion on what to use (`preBuildComponent`) instead.

* Update release-notes/Cabal-3.12.0.0.md

Co-authored-by: sheaf <sam.derbyshire@gmail.com>

Co-authored-by: brandon s allbery kf8nh <allbery.b@gmail.com>

Co-authored-by: brandon s allbery kf8nh <allbery.b@gmail.com>

Use alice as username in cabal path examples

* Add release notes for Cabal 3.12

Forwardport of #9785, #9908

Add changelog/release notes for Cabal 3.12 (#9785)

- generated with
     git log --pretty=oneline --no-color cabal-install-v3.10.1.0..HEAD > 3.12.prlog
- deduped
- stored WIP “release notes” file for future `cabal-install` release

3.12 changelogs updated (#9908)

* Update changelog for 3.12

(and for future WIP 3.12.1.0 cabal-install)

* Remove changelog.d files

* 3.12 changelog fixup (#9922)

* Incorporate Brandon’s suggestions

See #9920.

* Incorporate Artem’s suggestions

See #9920.

* Do not repeat yourself

* Fix whitespace

* Fix release notes grammar

See #9920.

Fix changelog/readme

Support GHC 9.12

Bump project version from 3.11 to 3.13

update zlib.cabal location

The upstream zlib package was recently reorganized in a way that
caused our git fetch test to fail. Update it to match.

Fix #8141 Don't refer to 'custom-setup' as 'optional'

Matthew Pickering authored 1 year ago and Rodrigo Mesquita committed 1 year ago

This makes `withShorterPathForNewBuildStore` fit more nicely into the
rest of the testing infrastructure.

* Move `withShorterPathForNewBuildStore` to `TestM` monad
* Move responsibility for passing `--store-dir` to `cabalGArgs` function
* Move `findDependencyInStore` into `TestM`, and remove requirement to
  pass path to store directory.
* Introduce `testStoreDir` function which returns the store location
  (and honours `withShorterPathForNewBuildStore`)
* Migrate tests which use `withShorterPathForNewBuildStore`.