Fix test for windows environment without git bash

Fix dll build for windows

Fix configuration of test directories that should not be direct

Fix for when DPAHT is configured in a docker environment

Fix failed to remove temporary directories

Fix test cases that fail to listen

Revert "Fix #2691: Use same structure for managed and unmanaged path" ...

This reverts commit 1a53049.

Fix #2840: Build collision for single-package and FILE_FULL_PATH ...

By including the package path in the buildid we avoid the problem,
at the expense of not sharing the cache for packages that could be
shared, but we would need to know if the code depends on __FILE__
and __FILE_FULL_PATH__ or not.

Merge remote-tracking branch 'upstream/stable' into merge_stable

CI: Move single checks to Github, remove dead code ...

Remove support for very old frontend - we were not testing it anyways.
Move the useful checks to another job so they run once.

test/use-c-sources: disable for gdc ...

Gdc doesn't support `#include`s in importC

Signed-off-by: Andrei Horodniceanu <a.horodniceanu@proton.me>

Allow building deprecated modules without deprecation warnings ...

The compiler issues a deprecation warning only on a
"non-deprecated" -> "deprecated" transition.  As such, building or
testing Dub packages which have deprecated modules when a
dub_test_root.d file needs to be generated will cause deprecation
warnings.

This in turn makes it impossible to use `buildRequirements
"disallowDeprecations"` in this situation.

Fix this by simply making the auto-generated root
module (dub_test_root) deprecated. As it is the compiler's entry
point, the module itself will not cause a deprecation warning, and it
importing deprecating modules will not cause deprecation warnings (as
there is no longer a transition of deprecation state).

Fix #2691: Use same structure for managed and unmanaged path ...

Currently, we issue a warning asking people to migrate, but the migrated
path is not actually recognized. It was suggested in the issue to ignore
this warning for add-path. However, as add-path is a rather low-level
use, I think it is better to impose the same condition for managed and
unmanaged path, in order to be able to provide the same guarantees.
For example, once we move to reading version from the path,
we can provide the same speedups for add-path users.
We can also make sure that add-path users don't have surprises when
dealing with packages that expect a certain structure outside their
directory, such as arsd and ae.
Some tests were updated with the new path, however, as many will likely
be rewritten with the new test framework, and a lot of tests are affected,
not all of them were updated, providing coverage for the old and new
code alike.

Fix issue #2190 - windows: dub won't run if TEMP is unset or empty

Fix issue #2190 - windows: dub won't run if TEMP is unset or empty

interactively query for license, suggest SPDX licenses (#1902) ...

Co-authored-by: Martin Nowak <code@dawg.eu>

add `dub describe --data=configs,builds` ...

supersedes the trivial part of #2204

Fix test/3-copyFiles project on Windows

Fix test/issue2452 project on Windows

CI: Enable test/run-unittest.sh on Windows

add "cacheArtifactPath" in TargetDescription ...

Allow 3rd party programs (e.g. Meson) to locate artifacts in the cache

add test for the --deep switch

Implemented recipe files for dub #2684 (#2685) ...

Co-authored-by: Jan Jurzitza <gh@webfreak.org>

test/issue895-local-configuration.sh: Update test ...

Failure mode is different as we're no longer asking the shell to run
the dummy program, we're doing it ourselves.

Fix failure of test suite on POSIX ...

failure due to change of escaping of posix paths in phobos

support specifying --d-versions ...

Usually you should prefer using configurations and build types, but
sometimes, especially when wrapped in other build tools or when
supporting e.g. different target platforms on the same target
architecture and configuration, you may want to manually manage certain
versions.

cache db test uses gitcompatibledubpackage

add test for the cache database

PackageManager: Store packages hierarchically, by version ...

As explained in the changelog, this hierarchy makes much more sense
than the current one, and will make it possible to read the version
from the directory name.

Don't depend on the whole of Vibe.d for the test_registry ...

Makes the code a bit more verbose, but remove the dependency to vibe-d:mongodb,
which happens to be the one currently failing on master.