Universal Tooling/Aliases and Hierarchy

Devtool could provide a cross-platform alias/tooling management platform to meet the needs of not only a single project, but an org, a specific host, or an individual developer.

• Project-based tooling, as always
• Host-based tooling that can be run anywhere on the machine, based on #20, basically sharable, pluggable aliases
• Org-defined tooling that applies to any of the org's projects/apps. Maybe this is just a plugin required by each of their projects
• User-defined tooling (.devtool.local.yml)
• Establish a hierarchy for overriding tooling so that a general org-based command can exist that can be overridden by a more tightly-scoped definition like host, app, local, or user.
• Maybe there should be separate local and user scopes so you can have config for a local environment, similar to a .env file used only on prod, then a user scope for a dev's personal preferences that overrides everything else.
• Maybe implement a concept similar CSS's !important to prevent overriding

The issue names no implementation files, tests, or entry points. Start by reviewing the existing tooling and alias configuration, then define the project, host, organization, local, and user scopes and their override order; done means the hierarchy and override rules are specified well enough to implement.