Rename UserConfiguration to Settings ...

The latter is more accurate, as we can have system settings
of type UserConfiguration.
This is also a push towards more consistent naming within dub,
as configuration is primarily used for package recipe 'configuration' field.

Move user settings to dub.data.settings ...

By moving it to its own module, we can ensure it's almost a leaf module.
We can also extend unittests to check different scenarios
without relying on integration test.

Move computeBuildID outside of BuildGenerator ...

It does not use anything from 'this', only its input parameters.
Additionally, change the order so it is usable with UFCS.

Rename localRepository to userPackages ...

The 'repository' terminology is confusing, and needs to be interpreted
from the PoV of the PackageManager to make sense. It is likely that
a naive read of this name would lead one to think of git repository,
as opposed to the repository where packages are stored.

Fixed dub init docs (#2537)

Improve dub init custom template docs

Revert "Remove Vibe.d HTTP support / library-nonet" ...

This reverts commit db49cbe.

Add nothrow attributes to dub.semver module

Replace all instances of mkdirRecurse with ensureDir ...

All usages actually want to ensure the directory is present,
and don't care about having a separation between existence check
and creation.

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

update version to v1.30.0

Merge pull request #2526 from dlang/add_path_workflow ...

Fix add-path based development workflow

Fix version match rules for add-path based packages.

Move foreign code from global scope to dub.internal. ...

Avoids conflicting with the actual dub packages when working with dub as a library. Also, even if just by convention, it ensures that dependent code doesn't rely on this code as a public API.

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

update version to v1.30.0-rc.1

Move existsDirectory next to existsFile ...

It doesn't make sense to have those in two separate modules.

Unify reading and writing files under a single API ...

This removes the range API and instead uses Appender,
while using a limited and centralized set of functions
to read/write from files.
The end goal is to permit dependency injection,
which is a pre-requisite to extending the test-suite.

Dub: Use removeFile instead of std.file.remove (#2516) ...

In the end it calls the same function, but this allow us
to consistently inject dependencies.

Remove Vibe.d HTTP support / library-nonet ...

library-nonet has been broken for years, and is not used.
Most importantly, it has no support for timeout.
Lastly, the likely reason it was originally introduced was to
avoid a hard dependency on cURL, something that has been fixed
in Phobos directly.

Make the test runner code more readable ...

Using manifest constant and a single format call,
the code will be more readable than piecemeal additions.

vibecompat/core/file: Publicly import path, not URL ...

We don't actually use URL here, nor should we,
we use path, so correct the import.

Path: Remove unused isValidFilename private function

Path: Add missing else clause on version statement ...

This was wrong on many level:
- The missing `else` clause meant that the `enforce` clause was always there on Windows;
- The `enforce("Reason")` should have been `enforce(false, "Reason")`,
  as in its current form it would never fail and not serve its intended purpose;
- It was pushing at runtime something that was easily detected at CT;

Fix #1752: Use 'no' as string representation of Dependency.Invalid

PackageManager: Load packages lazily on dub build ...

A problem of the current design of dub is that all locations are scanned,
regardless of what action is being performed, often multiple times.
With this change, a regular `dub build` on a project with all dependencies
resolved will no longer loads all available package, which can substantially
speed up development.

Use getPackage instead of getBestPackage for resolved dependencies ...

getBestPackage is intended to find the highest local version matching a range.
Due to this, it has to eagerly load packages and iterate through them.
However, when loading a resolved dependency, we have an exact Version,
which is simply wrapped in a VersionRange, so we can call getPackage instead.

Document PackageManager.getBestPackage, deprecate Dependency overload ...

The Dependency overload is not needed, as calling getBestPackage
with an SCM / path dependency does not make sense.

Deprecate `PackageManager.refresh(true)`, only expose `refresh()` ...

It is not actually used, as all call sites but two use false as an argument.
The two calls using true are inside a constructor, meaning there will be no
pre-existing packages, so whether true or false is passed will have
the same effect / result.

Deprecate yet another dub.remove overload using force_remove