Loading of "shared" config

[noizwaves]

After writing Scope configs for a couple of apps, I noticed many of the config files were very similar. What I'd like to do is deploy a set of re-usable configs alongside scope within Gusto. To do that, I'd like for Scope to additionally look for config files relative to it's current executable location.

Consider this example, where scope is deployed to some system path:

❯ tree some-system-path
some-system-path
├── bin
│   ├── scope
│   └── scope-intercept
└── etc
    └── scope
          ├── check-1.yaml
          └── check-2.yaml

In addition to loading from the local .scope directory, it would also load from <some-system-path>/etc/scope.

Plan

• Add the ${SCOPE_BIN_DIR}/../etc/scope path to the config paths loaded
• Allow recursing into sub-directories
• Expand how ScopeDoctorGroup action.check.paths are evaluated, so that application files (i.e. files not in proximity to the shared configs) can be specifically referenced