chore(path): Make a commonly triggered assert more verbose ...

We see this assert triggered frequently, even sometimes in production,
so at least make it easier to track down the data involved.

Fix skipRegistry parsing unittest ...

Contrary to the comment in the unittest, the code is checking for the
wrong value, should be `default_` not `all`. The unittest passed
because the function threw an exception not because of the value of
skipRegistry but because there's a missing '}'.

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

Merge pull request #2946 from ibuclaw/merge_stable ...

update version to v1.39.0-beta.1

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

update version to v1.39.0-beta.1

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

Merge pull request #2945 from ibuclaw/merge_stable ...

update version to v1.38.1

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

update version to v1.38.1

Merge pull request #2944 from Geod24/mlang/FSR ...

Refactor filesystem abstraction to and use it in production 

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

Filesystem: Provide the string writeFile overload at the interface level ...

The string overload is just a convenience function and there is little
chance that it wll ever need to be overloaded.

MockFS: Simplify existsFile / existsDirectory

MockFS: Simplify implementation of setAttributes / setTimes ...

Hoist the lookup from FSEntry to MockFS to reduce the duplication.

Refactor filesystem abstraction to and use it in production ...

The filesystem abstraction needs to be known to production to avoid
too much code duplication. So far we have used functions in
`PackageManager` that the `TestPackageManager overrides.

With this change, we can remove them, and instead just pass an interface.
On the long run, we should be able to do dependency injection simply
by passing a different object (or overriding) the `Dub` class.

An initial attempt made `FSEntry` inherit from the `Filesystem` interface,
however that attempt was doomed as it conflates two different abstractions:
`FSEntry` is a "node" in the filesystem, which we want to act on in one
of multiple ways: move to another node, or take an action. On the other hand,
`Filesystem` is a more generic interface and takes a path as most of its
function's argument. A `path` and an `FSEntry` have a lot of overlap
(they are a reference to a node in a tree) and the resulting interface
would have been very clunky.

Trivial: Pass an absolute path when building TestDub in legacy UT ...

This way we avoid a call to getcwd.

Merge remote-tracking branch 'upstream/stable'

CI: Reduce dependency on std.path / std.file in one unittest ...

This will make migrating to the abstracted IO much easier.

Drop support for LDC v1.26.0 ...

We only support the last 10 versions, so LDC should have been upgraded in the previous PR.
In addition, we can remove a superfluous __VERSION__ statement, which haseen superfluous
for quite a while now.

Upgrade CI configuration following macOS-11 deprecation ...

macOS-11 is going away at the end of June.
As a consequence, we upgrade to macOS-12, upgrade the supported
frontend versions, and add some arm64 tests to prepare for
future upgrades.

Trivial: Remove an extra whitespace in CI file

CI: Adapt pr_info_post to github-script v7 breaking changes ...

Since v5, the method have been moved. This is not caught by CI as it
only uses the workflow in the master branch.

CI: Correct version for sticky-pull-request-comment action ...

This was not caught by CI because it doesn't take effect before merging.

CI: Upgrade some more actions to their latest versions

CI: Only attempt to upload coverage reports with COVERAGE: true ...

Otherwise we get a flurry of warning in GitHub.

Look up `dub.selections.json` files in parent directories too (#2272) ...

* Look up `dub.selections.json` files in parent directories too

In case the root package directory doesn't contain a `dub.selections.json`
file, look in parent directories too and load the first (deepest) one.

This allows using a 'central' `dub.selections.json` file for a repository
containing multiple dub projects, making it automatically apply to all
builds in that source tree if located in the repository root directory
(unless a local `dub.selections.json` overrides it).

Such an 'inherited' selections file is never mutated when running dub for
a nested project, i.e., changes are always saved to a *local*
`dub.selections.json` file.

Upgrade vibe-d dependencies ...

This brings in vibe-core 2.8.5 which contains an important
fix needed for a new feature.

Merge pull request #2932 from ibuclaw/merge_stable ...

merge stable

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

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

update version to v1.38.1-rc.1

LDC: Don't keep around temporary object files for static libs (#2690) ...

* LDC: Don't keep around temporary object files for static libs

This was a workaround for older LDC versions. Since LDC v1.25,
`-cleanup-obj` implies that the temporary object files are placed
into a unique temp directory (per compiler invocation), so that
object file collisions across parallel dub invocations cannot happen
anymore.