Need a way to have per-machine profiles in settings

Settings roam, which is really cool! However, my machines don't all have the same configuration. For instance, my main dev machine has tooling installed on the O: drive. My default profile runs the VS command prompt batch file. Well, I just dropped terminal on a second machine that doesn't have the same hardware config, so this default profile is totally busted there. Thankfully I'm launching with cmd /k o:\...foo.cmd, so I just get a slightly annoying error from CMD.

However, we'll need a way to have some way of differentiating config. As an idea, in other tools (e.g. emacs), it's not uncommon to key off of machine name to vary configuration.

=========

After a brief discussion in triage, we realize that there's going to need to be a thorough design of how we want per-machine settings to be done here.

The initial design of settings is "simple" in that all settings applied in an unfiltered fashion and there's only 1 file and we have no "settings UI yet".

There's advantages to no settings UI.
There's advantages to having only one settings file.
There's advantages to being able to layer multiple settings files.
And so on and so forth.

Therefore, it's a feature that someone needs to sit down and spec at a future date.

No implementation file or test is named. Start by reviewing the current settings model described in the issue: one unfiltered settings file and no settings UI, then use the triage discussion to scope machine-specific or layered settings. Done means an agreed specification for how per-machine settings should work.