feat: add cultureinfo to reader/writer settings.

[ByronMayne]

About the PR

The unit tests are currently failing to run on linux but work on windows due to differences with date time parsing and newlines. In this PR I have done the following

• Created a static Configuration class that contains common settings used across all the project
  • Contains CultureInfo instead of being hard coded across the code base
  • Contains DateTimeFormat which is explicitly ISO 8601 and used for reading and writing
• Removed StringExtensions.cs and instead opted for extending Fluent Assertions FluentAssersionExtensions
  • Across all unit tests the same functions were used for fixing new line characters. Instead of doing this I extend fluent assertions which cleans up the code.
• General Test Cleanup
  • Moved some of the inline test data into stand alone files. Having massive text embedded in code makes they really hard to read and follow up on.

Changelog

• Add: DataTime is always read and written using ISO 8601 format

Follow up questions

• The unit tests currently all tests everything in one go rather then individual components. When they break it is very tedious to figure out which part went wrong. Are you against breaking them apart?
• Across the application there is a few one off static helpers JsonHelper, YamlConverter, and previously StringExtensions. Would it make sense to combine them into either the Configuration in this review or have them as an instance that is passed around as a context?

[ByronMayne]

As per usual feel free to push back on anything you don't agree with :)

[VisualBean]

Only a few things, but otherwise I am happy with it

[VisualBean]

Definitely not against splitting unit tests apart.
I think we should add a document test for the kafka streetlights example as a default document test, and migrate everything else out into smaller units, for sure.

[VisualBean]

Thanks a ton @ByronMayne, great addition to the project.