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

Commandline: Do not duplicate GeneratorSettings fields ...

Instead of adding fields individually to the Command, just store a GeneratorSettings,
and getopt it as needed.

use json.get directly instead of casting ...

see https://github.com/dlang/dub/pull/2321/files#r928547114

Use Configy to read dub.selections.json

compilers: Change lflagsToDFlags to avoid scope escape ...

If 'in' implies 'scope', then the parameter is being escaped.

Unify package path in a single PackageManager function ...

The idea is that PackageManager should be responsible for packages on the disk,
and the first step to do that is remove the leakage of path happening in the Dub class.

Move PlacementLocation from project to PackageManager ...

PlacementLocation define which local path is used for storing packages.
It has nothing to do with project (it's not even used there),
and should be contained inside PackageManager, even if currently
quite a few details are leaking all over the place.

Merge pull request #2340 from Geod24/10-years-anniversary ...

Remove long-deprecated 'install' and 'uninstall' command

Signed-off-by: Nicholas Wilson <thewilsonator@users.noreply.github.com>
Merged-on-behalf-of: Nicholas Wilson <thewilsonator@users.noreply.github.com>

Trivial: Deprecate Dub.remove(Package, bool) ...

The corresponding PackageManager function is long deprecated,
but the Dub wrapper was not deprecated.

Remove message about system installation of packages ...

This is no longer true, we have /var/lib/dub
Moreover, users should be familiar with this, as it's how most package managers work.

Remove long-deprecated 'install' and 'uninstall' command ...

There were deprecated before dub v1.
I stopped going up the history after 4d8f81b,
on 2013-11-13, where they were already deprecated.

Do not call Project.reinit from commandline ...

reinit is called directly when Project is instantiated. It calls PackageManager.refresh,
which re-reads all packages stored in the package directory.
If we want to make dub smarter and faster, we need to stop scanning all the packages
on disk when we have a resolved dependency tree, and move to a lazy/on-demand approach.
The first step would be to remove this call. See also #2388.

SpecialDirs: Re-order by priority, document

Refactor SpecialDirs initialization in its own function ...

Take the IO-performing code in a single function so later on
we can better isolate it for library users.

Trivial: Fix syntax for Params documentation in packagesuppliers

Trivial: Deduplicate GeneratorSettings initialization

Trivial: Streamline code when package not found in project ...

Instead of checking the same condition three times,
just do it one, and make it more obvious we're actually
handling different kind of Dependency.

Fix missing sanitizing of subpackage targetTypes ...

A regression introduced in #2277.

Dependency: Remove dead 'isSCM' code from Version ...

Before `Dependency` was made to use `std.sumtype`,
the code was piggybacking on a field `VersionRange m_range` to store
the git reference whenver the `Dependency` was a `Repository`.
Since this is no longer the case, we can remove this exception from `Version`.

Dependency: Convert to a discrete type ...

A major issue when dealing with the 'Dependency' type is that it evolved from a simple type,
which stored a version range and perhaps one or two boolean,
to one that stores 4 kinds of dependencies: version range (including exact version),
branches, repository + hash, and path.
Instead of using a discrete type (e.g. a tagged union), the type is a mix of style,
and repository and branch are piggybacking on the field used for the version range.

Switching to std.sumtype makes interaction between fields more obvious.
Most importantly, it forces the programmer to answer the hard questions,
such as how do we compare completely different dependency (version vs repository).

Hopefully this will make the code easier to understand, and in the future,
make it easier to add a new kind of dependency.

Add VersionMatchMode support to VersionRange.matches

commandline: Catch Exception, not Throwable ...

So that assert errors, which are bugs in dub, get properly reported.

Suppress `version` for path-based deps in Dependency.toJson() ...

As in dub v1.29 and before.

Fix missing deserialization of fileVersion from dub.selections.json ...

A regression in master, which can lead to `dub upgrade` generating an
invalid dub.selections.json (with fileVersion = 0).

sdl: Simplify Dependency parsing ...

Don't warn on ignored version specification, json doesn't do this.
Also fully replace the instance instead of editing piece-meal,
it makes the code clearer.

Trivial: Remove a leftover debug statement

Dependency: Remove top-level safe, apply to decl ...

A top level safe means that we cannot have templates in this structure
that infer their safety, which can be severely limiting.

Dependency: Change format for path-based dependencies (#2316) ...

* Add missing attributes to NativePath.empty

* Dependency: Change format for path-based dependencies

Deprecate duplicated JSON serialization for Dependency

Deprecate `PackageManager.loadSCMPackage` & other `Dependency`-related refactoring (#2312) ...

* Trivial: Take a nested function out of a foreach loop

* Deprecate PackageManager.loadSCMPackage's Dependency overload, use Repository

We're moving away from using `Dependency.m_range` to store the git ref,
and the `Repository` type has already been updated to include the information,
but some places still read it from `m_range`, including this one.

* Trivial: Forward Dependency's string ctor to VersionRange ctor

* Trivial: Simplify comparison with `VersionRange.Invalid` within `VersionRange`