Because ${FOO} is already expanded in the Makefile, which leads to
syntax errors in the CI when secrets are replaced by ***, we need to
use $${FOO} so expansion only takes place in the shell.

There is a new make file,

    doc/Makefile

that defines these goals:

  - `check-requirements`:
    Check `requirements.txt` for security problems (CVEs) using `skjold`.
    This goal is intended for the "Users guide" CI.
    SKJOLD_GITHUB_API_TOKEN might have to be set if GITHUB_TOKEN is
    not in the environment, in order to access the GitHub GraphQL API.

  - `build-and-check-requirements`:
    Rebuild `requirements.txt` from `requirements.in` using `pip-compile`,
    and check with `check-requirements`.
    This goal is intended for manual invocation.

    It is invoked from the top Makefile via goal
    `users-guide-requirements`.

Alternatively, these goals could be coupled with the doc build
`make users-guide`.
However, since these goals require a couple of seconds to run, I think
it is annoying to call them on every build of the documentation.

fix curl auth on upload

Resolve #7765: Add -c alias for --constraint cli argument

Fix #7777: upgrade requirements.txt to latest versions

This is done via specifying the basic dependencies in `requirements.in`
and then use `pip-compile` to generate the full "build-plan" in
`requirements.txt`.

From: https://modelpredict.com/wht-requirements-txt-is-not-enough

Make cabal init conform with `--no-comments` flag for commented fields

Remove any remnant of the 'world' file

In v1-install, 'world' was used to trace what packages have been
installed, and re-install on-demand everything listed in it. However, in
v2-install, this is no longer needed and this file leads to code bloat.
Additionally, 'world' code-path is probably not up-to-date, remove it instead of
having partial features.

Updated getting-started tutorial and CLI docs to reflect current operation of `cabal init` command.

Co-authored-by: Javier Neira <atreyu.bbb@gmail.com>

Support Git submodules in source-package-repository

The `RepoRecipe` type now takes a type level argument which tells the arbitrary
instance whether to allow submodules in the recipe or not.

* glob expand extra-src-files when tracking for rebuild

* changelog

Co-authored-by: Gershom Bazerman <gershom@arista.com>

Avoid using duplicate global config not adding it in the dummy project context

* Afaics all establishDummyProjectBaseContext uses in the codebase
(CmdInstall, CmdRepl and CmdRun) are guarded by
ProjectOrchestation.withProjectOrGlobalConfig and it is already
adding the global config
* Changed the argament name from cliConfig to projectConfig to make
clear it includes the config from more sources than the cli.
* Added an argument comment to make clear client code *must* include
the global config if it is needed

* Debug package hash inputs

* Add test skeleton for #6906

* Improve output of hash inputs

* Add tests over pks hash inputs

* Correct typos and formatting

* Add missing do

* Add missing cabal result arg

* Make consistent log about hash.txt

* Update log msg creating file

* Change var name to hashFileName

Remove unused ConstraintSourceModifiedAddSourceDep

Select buildable targets

Remove ConstraintSourceSandboxConfig

because we do not provide sandbox functionality anymore

Fix #5410: include `unpack` in help text as deprecated alias for `get`

```
$ cabal --help
...
 [package]
  get               Download/Extract a package's source code (repository).
  unpack            Deprecated alias for 'get'.
...

$ cabal unpack --help
Deprecated alias for 'get'.

Usage: cabal unpack [PACKAGES]

Creates a local copy of a package's source code. By default it gets the source
tarball and unpacks it in a local subdirectory. Alternatively, with -s it will
get the code from the source repository specified by the package.

Flags for unpack:
 -h, --help                     Show this help text
 -v, --verbose[=n]              Control verbosity (n is 0--3, default
                                verbosity level is 1)
 -d, --destdir=PATH             Where to place the package source, defaults to
                                the current directory.
 -s, --source-repository[=[head|this|...]]
                                Copy the package's source repository (ie git
                                clone, darcs get, etc as appropriate).
 --index-state=STATE            Use source package index state as it existed
                                at a previous time. Accepts unix-timestamps
                                (e.g. '@1474732068'), ISO8601 UTC timestamps
                                (e.g. '2016-09-24T17:47:48Z'), or 'HEAD'
                                (default: 'HEAD'). This determines which
                                package versions are available as well as
                                .cabal file revision is selected (unless
                                --pristine is used).
 --pristine                     Unpack the original pristine tarball, rather
                                than updating the .cabal file with the latest
                                revision from the package archive.

Examples:
  cabal unpack hlint
    Download the latest stable version of hlint;
  cabal unpack lens --source-repository=head
    Download the source repository of lens (i.e. git clone from github).
```