Support defining and merging multiple configs

[caitlinelfring]

Is your feature request related to a problem? Please describe.

Woke only lets you define a single config file. It should support defining and merging multiple config, especially now that there is support for defining remote configs.

Describe the solution you'd like
woke -c https://example.com/config1.yaml -c https://example.com/config2.yaml -c local.yaml where all three configs are merged

Describe alternatives you've considered

Additional context
This will open up a lot of options for community-driven rule sets and allowing users to pick and choose which rules they want easily by choosing from an array of different configs. This will also enhance the "exclude category" feature even further #121 (comment)

[nicorikken]

My main use-case would be to merge curated rules. Besides the default rules I'd like to refer to other rulesets that are drawn from organizations focused on inclusive language or simple language. In my case I also want to check the Dutch language, which might not be relevant to all others. So besides merging complete configs, how about adding the ability to merge rulesets? A configfile might add more than just the wordlist which might be unwanted. Multiple rulesets would also make it easier to break up rulesets in sections for different use-cases. In terms of implementation I would then allow linking to local or remote rule files from the configfile, or allowing users to specify rulsets with one or more -r flags. Then again, just merging full configfiles would still work as long as people only specify the rules and leave out a config of ignore_files and success_exit_message.

[nicorikken]

In Woke Config Builder I use Conflate to combine multiple Yaml files into one. In the process I discovered that it is also convenient to combine ignore_files, so in that regard it makes sense to combine complete configs into one.