Provider inheritance?

[theutz]

I'm not sure that this is a bug, since there's definitely some concerns around behavior to be thought through. But I'll put it here anyways since fnox didn't behave as I expected.

Steps to Reproduce

fnox init # follow wizard to setup age
fnox set MY_SECRET parent
mkdir child
cd child
fnox init # skip setting up provider
fnox set -c fnox.toml MY_SECRET child # even if you specify the child it writes to the parent
fnox list -V # outputs "child"
cd ..
fnox list -V # outputs "child", because the parent value was overwritten

The fnox edit command seems to be aware that it doesn't know what to do when no provider is setup, but fnox set didn't warn me at all.

[jdx]

This is the same underlying issue as #104 and is fixed in #122.

fnox set now always writes to the local config file, creating a local override if the secret exists in a parent config. This prevents the unexpected behavior of silently modifying parent config files.