* Handle 3D Slicer licence

* Update SPDX license list to version 3.25

* Remove changelog entry

We don't need it, changes have been manually
incorporated in 3.14 release notes (#10338)

---------

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

* Add OrPatterns extension

* Add changelog

* Add missing full stop

* Add missing NoMultilineStrings in vim syntax file

* Make test happy

* Remove changelog entry

We don't need it, changes have been manually
incorporated in 3.14 release notes (#10338)

---------

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

Remove read-only mark on `dist-newstyle` when doing `cabal clean` on Windows

Some git files are marked as read-only. To ensure we delete the folders we are
supposed to, we first remove the read-only attribute via `CMD.exe`, then we
forcibly delete the relevant directory.

Warn that scripts cannot be package executables

Bump deepseq bounds to allow 1.6

* Bump version numbers to 3.15

* Bump GHC 9.6.6 for workflows

* Update index-state

* Bump bootstrap boundaries

* Regenerate bootstrap files

Fix `cabal-install:long-tests` with Git >=2.38.1

Closes #10312.

Git 2.38.1 and newer fails to clone from local paths with `fatal:
transport 'file' not allowed` unless `protocol.file.allow=always` is
set.

This is not safe in general, but it's fine in the test suite.

See: https://github.blog/open-source/git/git-security-vulnerabilities-announced/#fn-67904-1
See: https://git-scm.com/docs/git-config#Documentation/git-config.txt-protocolallow

`validate.sh`: Use Bash explicitly

We were already relying on Bash features like `echo -e`, so let's make
it official.

validate.sh: `--jobs` should default to `nproc`

If `nproc` is available and `--jobs` is not given, this will use the
output of `nproc` as the value for `--jobs`.

Otherwise, the old default value of 4 will be used and a warning will be
printed.

The default value of 4 has remained unchanged since it was added in
6a9a101c in 2018; that may have been a
reasonable number of cores then, but my development machine today has 20
cores, so setting the parallelism to 4 leaves a lot of performance on
the table!

Custom-build: Document breaking change on built comps.

As mentioned by e8c9d194, Cabal 3.12 introduced a breaking change where
an unnecessary (not requested) component of a package with a "Custom"
build-type is no longer built.

This caused breakage for Agda, and was undocumented.

The behaviour, despite breaking, is the desired one -- a package
shouldn't assume the executable will be built if only the library was
requested. This commit documents the breaking change to make sure it is
more visible.

In the meantime, we've also patched Agda to no longer expect the
executable to be built when only the library is installed.

Closes #9777 and #10235

Bumps [actions/cache](https://github.com/actions/cache) from 3 to 4.
- [Release notes](https://github.com/actions/cache/releases)
- [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md)
- [Commits](https://github.com/actions/cache/compare/v3...v4

)

---
updated-dependencies:
- dependency-name: actions/cache
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: brandon s allbery kf8nh <allbery.b@gmail.com>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

Support ARM / M1 macOS in `validate.sh`

Do not advertise `git://` in docs

Fix Windows tests depending on scripts

* Improve bat scripts for CCompilerOverride

* Ensure Windows tests can cleanup the temp directory

* Implement `flaky` combinator

* Remove outdated tests

* Remove broken tests

These tests were testing for messages that were removed with the `cabal check` rework.

* Make `skip` and `broken` messages uniform

* Mark flaky tests

* Re-enable DeterministicTrivial

* Fix MacOS canonical paths

* Extend cabal-testsuite readme with `flaky`

* Skip non-terminating tests in Windows CI

---------

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

Re-enable Windows CI

CI: validate: don't fail-fast

Which means that if a Windows job fails, all other jobs in the matrix
will be allowed to finish (other platforms, as well as other compilers on Windows, etc.)

Inspired by the discussion at https://github.com/haskell/cabal/issues/10263

make sure cabal-install is compatible with Cabal

See https://github.com/haskell/cabal/issues/9833

If a ghc ships with a compatible Cabal, it will be preferred by
the solver on `cabal install cabal-install`; the new `cabal-install`
should in fact be compatible. So we test this on release branches
that have had at least one release on Hackage. (Ideally we'd check
ghc instead, but we can't do that from GHA. Even checking Hackage
is pretty painful.)

Collection of patches to do with --working-dir 

Before the previous patches this test failed because an incorrect path
was passed to hsc2hs (a preprocessor), it now succeeds :)

When testing `./Setup` only, when `withDirectory` is used, instead of
changing into that directory when invoking processes, we now use the
`--working-dir` flag and keep a fixed CWD.

This will therefore passively test that `--working-dir` is working

In addition, it makes it possible to test things easily such as
`--working-dir` with a relative path as an argument. `cabal-install`
will only invoke `--working-dir` with an absolute path and hence is
isolated from any double interpretation issues.

Testing against these double interpretation issues is very important as
it also prevents over-interpretation of relative paths into absolute
paths. Passing absolute paths to tools such as hsc2hs can lead to the
build directory leaking into an interface file which leads to
non-reproducible results.