Butler V2 suggestions

Today you can specify the following values:
```
primary-config-name - name of merged files
primary-config - list of files in repo section to be merged into the primary-config-name
additional-config - just files to be put in place as is
```

What might be better is to do away with that, and enable the following flags in the `repo` sections
```
merged = true
merged-file = "filename"
```

That way it'd be easier to understand what is going on there. If the repo is set to merged true, then all the files that it downloads will be merged.

Another thing that would have to change with this is that for the http/https handler, you'll want to be able to specify the actual host to hit. If the URL doesn't exist, then use the repo name (which is default now.)

The reason for this is that if you want to hit the SAME repo yet have it merge, then that'll break the TOML config, since how it nests the configuration, you'll have duplicate repos. At that point you would need to have the repos have arbitrary names, and specify the host further down in the http settings.

Start by tracing how repo sections are parsed and how the http/https handler selects a host. Review the current primary-config, primary-config-name, and additional-config behavior before deciding how merged and merged-file should interact with duplicate repositories. Done means the configuration model and host selection support the proposed cases without ambiguous TOML nesting.

Written by the indexing model from the issue text.