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.

Expand selections file handling to handle new versions ...

Up until now, the selections file has had a `fileVersion` in it,
but that number was always stuck to 1.
In order to make it possible to handle more than one version,
a bit of scaffolding needs to happen in the config parser.
This lays the ground for a version 2 of the selections file.

Trivial: Reduce import scope in dub.recipe.selection

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.

Minor: Align dub.recipe.selection style with dub.recipe.packagerecipe ...

During review of the PR that switched PackageRecipe parsing to use Configy,
WebFreak pointed out that having an internal, private structure used for
parsing YAML field was preferable to having it at module level.
This aligns the names and the approach used with the one in PackageRecipe.

Configy: Replace parseField with parseAs ...

This removes the need to keep the representation around and have
it stored in a field of the enclosing struct.

Use Configy to read dub.selections.json

Various code simplification around `dub.selections.json` (#2311) ...

* Deprecate unused Json constructor

* Trivial: Fix import order in dub.project

* Simplify DependencyResolver filtering

DependencyResolver is only instantiated from one place, and never re-used.
It makes more sense to set those variables in the constructor,
and avoid repeatedly calling a single function.

* Move file format to dub.selections.json to its own struct

Our goal is to replace the handcrafted JSON code with configy.