We should not be incrementing the AssemblyVersion of the Configuration library to maintain SemVer compatibility - only NuGet version and assembly file version.

The idea is that breaking changes should increment the major, so from 1-2, or both the assembly version and file version;

But new features, bug fixes, etc. only increment the file/nuget version, NOT the .NET assembly version.

Otherwise scenarios like PowerShell will not work with NuGet updates if other components have a dep. on the config dll.