Completion for flags does not have to be handrolled here, and I can use
the same struct strategies. I will have to rethink context usage, but
this will work in the long run, considering the track record of GitHub
CLI (gh) and Hugo and other large applications using Cobra.

Well, turns out making --config and --color-always persistent flags
broke other commands using "-c" and "-C" shorthands, so I
removed them for now, since they should be rather uncommon to use
for most people.

Also, I forgor to update the Nix hash. Oops. I fucked up. Lol.

This is rather buggy when the option argument is empty, but I'll worry
about it later.

This makes more sense for the scoring scheme for the fuzzy package being
used. Originally when using `zf` in Zig, this would return higher
numbers for less relevant results; this is the opposite, and only uses
integers, while also allowing negative numbers for very irrelevant
results.

…ch for it

The name "config" for the settings for `nixos-cli` is rather confusing.
Change it to `settings`

Flags like --max-jobs can also take zero as a valid value, and this
was impossible to pass on the command line earlier, since 0 is the
zero value and can also mean "unset". This differentiates them based
on if it was parsed in Cobra or not.