Fail upon encountering unrecognized fields in the config

[fsoikin]

Description of the change

(partially) fixes #1165.

The codec library doesn't have such feature, so I basically had to reimplement the relevant functions.

Unfortunately, this change doesn't affect some sections of the config, because their types and codecs are defined in the Registry library. I am planning to contribute the change back to the codec library and then migrate the Registry library to it.

Checklist:

• Added the change to the "Unreleased" section of the changelog
• [ ] Added some example of the new feature to the README
• Added a test for the contribution (if applicable)

[fsoikin]

And immediately we have a winner!

Turns out spago bundle has a command-line parameter for source maps, but not a config parameter. Another bug.

[fsoikin]

Or not a bug? Technically this can be specified in extra args, as I did here, but this is asymmetry. Not sure what the overarching philosophy is here.

[f-f]

Great catch!

Overarching philosophy is that we try to keep flags and config params as close to each other as possible. There are some notable exceptions, but this one is a bug: we should have a config parameter as well.

[f-f]

P.S. your commit messages for the autoformatter are extremely amusing, please keep them coming ❤️

[f-f]

Code looks good - we shall wait for the upstream codec-json lib to merge the patch so we don't have to keep the library code in here

[fsoikin]

Alright, upstream libraries finally updated, this should be ready now.

Sorry for the force-push, somehow my history wasn't matching GitHub, I must have rebased long ago, when I touched this PR last time.

I decided not to port:

• Codecs under Docs.Search, because the JSON files there are not written by the user.
• Spago.Config.remotePackageSetCodec - this is used to read package set from both local files and network responses, and I think that making it strict would break backward compatibility: if the server adds new fields, old clients won't be able to read responses anymore. Plus, there is no danger of typos here, because all fields are mandatory.
• Spago.Purs.moduleGraphNodeCodec and codecs in Spago.Purs.Graph - same reason. This is used for reading purs responses.
• Spago.Command.Ls.formatPackagesJson.packageCodec - used only for output.
• Spago.Command.Registry.search.infoDataCodec - used only for output.
• Codecs in Spago.Psa.Types - used to parse PSA output, same reason as for purs and remote registry.

[fsoikin]

I'm not sure what's going on here. Looks like it used to be JSON, but now it's YAML. I don't think I changed anything in that regard.

[fsoikin]

Oh, I see, this is #1280

[fsoikin]

Ok, this is looking better now.

[f-f]

We should use the latest, fc203a9e2a0b96a90ace20dc6958c157cbbca16b