Changelog for toml-parser-1.3.1.2

Revision history for toml-parser

Bugfix: In some cases overlapping keys in inline tables could throw an exception instead instead of returning the proper semantic error value.

Make more structured error messages available in the low-level modules. Consumers of the Toml module can keep getting simple error strings and users interested in structured errors can run the different layers independently to get more detailed error reporting.
FromValue and ToValue instances for: Ratio, NonEmpty, Seq
Add FromKey and ToKey for allowing codecs for Map to use various key types.

Added Toml.Pretty.prettyTomlOrdered to allow user-specified section ordering.
Added FromValue and ToValue instances for Text
Added reqKeyOf and optKeyOf for easier custom matching without FromValue instances.

Remove FromTable class. This class existed for things that could be matched specifically from tables, which is what the top-level values always are. However FromValue already handles this, and both classes can fail, so having the extra level of checking doesn't avoid failure. It does, however, create a lot of noise generating instances. Note that ToTable continues to exist because toTable isn't allowed to fail, and when serializing to TOML syntax you can only serialize top-level tables.
Extracted Toml.FromValue.Matcher and Toml.FromValue.ParseTable into their own modules.
Add pickKey, liftMatcher, inKey, inIndex, parseTableFromValue to Toml.FromValue
Replace genericFromTable with genericParseTable. The intended way to derive a FromValue instance is now to write:
```
instance FromValue T where fromValue = parseTableFromValue genericParseTable
```

Add Toml.FromValue.Generic and Toml.ToValue.Generic
Add Alternative instance to Matcher and support multiple error messages in Result
Add Data and Generic instances for Value