Verify that client config merging is working

[spkane]

Some testing appears to suggest that the merging of a client config in the local directory (for something like a git repo) is not currently working.

Verify this and fix it if required.

In all actuality we should walk up the filesystem looking for the first config that we find, to merge with the primary config file (or use if no primary is found)

[spkane]

Basically, If I have a cludo.yaml in the current directory, it should be merged with my normal cludo.yaml so that a local directory can primarily override the target.

[goonzoid]

Yeah, looks like this is currently broken.

A couple of thoughts / questions:

• Do we want to support a case where the client user only has a single config file in their local directory?
• What is the correct order of precedence for the other locations that the "normal" config file should be found?

[goonzoid]

Also just noticed #103 which is related. Going to take a step back and see if I can document the expected behaviour with regards to all things config related.