Windows: Don't copy import .lib & .exp files for executables ...

One aspect of issue #2377 - copy those for DLLs only.

Forward flag `--color={on,off}` to compiler calls (#2382) ...

When the user sets the color mode explicitly,
we forward it to the compiler for consistency,
while making sure it doesn't impact the build cache ID.

Fix #2348 Crash when describing postBuildCommands

Use SHA256 in place of MD5 in computeBuildName

improve some output coloring ...

See #2347

Address review by WebFreak001.

Keep logging functionality out of the public API as requested in https://github.com/dlang/dub/pull/2124#issuecomment-813016939.

Fix/Update some tests and make some info messages more similar to original version of Dub

Fix indentation style, now using tabs

Fixed blue color missing for config in up-to-date

Making the output prettier - first changes

New logging module - initial functionality ...

The new module replaces dub.internal.vibecompat.core.log by using the
same function names, but implementing colored output and the left
fixed-width tag. Overloaded functions are provided to output colored
text.

Still missing initLogging() and non-TTY stdout/stderr detection

Make Project.addTestRunnerConfiguration() accept a const GeneratorSettings argument

Refactor checks for platform is Windows into a method on BuildPlatform

Fix issue 2258 and copy the build artifacts to the target directory

Define the $DUB_BUILD_PATH variable. ...

The `$DUB_BUILD_PATH` variable is now defined inside the `postBuildCommands`
section. It contains the absolute path in which the package was built, and can
be used to copy by-products of the build process to their intended locations.

move command variable substitution to execution ...

This is needed as commands that need to be run need to have generator
settings available before running to avoid inconsistencies with
environment variables passed to the actually ran program and variables
used in substitution.

Fixes #2192

Fixes pre/postGenerateCommands inconsistently using dub environments
(execution was substituted including buildEnvironments, but shell cmd
did not get the build variables for substitution) - now both get
the build variables. Solved by removing code duplication. (env building)

This commit changes the behavior of `dub describe` so that describing
commands settings no longer substitutes variables. Before, known
variables would have been replaced in the output and on unknown
variables `dub describe` would fail with an error
`Target 'x' doesn't exist`

Now exposes some previously private project.d processVars functions

Windows: Copy .pdb files ...

Fixes #1962.

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

Don't reduce the max path length on Windows even further ...

Fixes #2143.

Add environment variables to BuildSettings (#2121)

Set cwd on spawn functions instead of chdir ...

It is more hygienic to use the cwd argument as it doesn't impact
the running process, and doesn't decouple the reason for it.

Remove redundant code with relativeTo ...

The versioned code was doing almost the same thing as relativeTo,
but adding `./` or equivalent so it could be run from the cwd.
Instead of doing this complicated patching, just use the absolute
path for running, but the relative path when issuing messages to the user.

Use compiler version, not frontend version for build IDs and paths ...

This prevents artifacts from being reused after upgrading the compiler
from a beta to a final or to a newer patch release.

cache the generated test main file: dub_test_root.d ...

these changes prevent dub from rebuilding a project every time it runs a unittest.

Replace occurences of 'in ref' with 'const scope ref' ...

In support for dlang/dmd#11000

Fix local cache

Remove some unused variables ...

There are plenty left, but those ones didn't seem to have any side effect.

Fix unnecessary rebuild of single file package

Include import paths in build ID. ...

Otherwise the same package with a different set of dependencies (or dependency versions) may get the same build ID, leading to linker errors.