Global default configuration

[jebentier]

Problem statement

The ability to configure the default qlty.toml to use, rather than the static default. Helping larger organizations (with 100+ repos) maintain and add new default plugins for languages without needing to edit every repo's qlty.toml manually.

Solution brainstorm (optional)

Some tools like GitHub allow for a .github repository to use as default configuration for any repository, following that approach of having a .qlty repository for default qlty.toml definitions to exist would be one way to solve this. Additionally it could work like rubocop's inherit_from support, which allows someone to define once, a default to start from, and use the remaining definitions as overrides to that default.