Currently included scopes are named from the parent scope and the relative path to the parent scope. This change allows for naming an included config scope with a user specified name. This makes it possible for users to include arbitrary directories with short semantic names.

ie. .spack/configs/include.yaml

include:
  - path: /path/to/my/project/configs/
    scope: project

Currently the scope naming looks like this

$ spack config scopes
...
user:/path/to/my/project/configs/
user:/path/to/my/project/configs/:deployment
user:/path/to/my/project/configs/:develop

The output renaming the included scope to project would look like this

$ spack config scopes
...
project
project:deployment
project:develop