Validate configuration

[dokterbob]

Checklist

• My issue is specific & actionable.
• I am not suggesting a protocol enhancement.
• I have searched on the issue tracker for my issue.

Description

It currently seems possible to feed ipfs config erroneous keys, which will be added to the configuration file. This can lead to unexpected behaviour in case of typos/configuration errors, e.g. in automated deployments.

What I would expect is that IPFS commands will fail with a (documented) non-zero exit status for invalid configuration keys and/or values.

Example

Correct key

% ipfs config --json -- Provider  '{"Strategy":"sdfsd"}' &&  ipfs config --json -- Provider; echo $?
{
  "Strategy": "sdfsd"
}
0

Incorrect key

% ipfs config --json -- Provider  '{"Strategies":"sdfsd"}' &&  ipfs config --json -- Provider; echo $?
{
  "Strategies": "sdfsd"
}
0

In addition, ipfs commands will not err and merely ignore invalid/additional configuration keys.

Possibly related: #8925, #8776, #8993