Merge branch 'bugfix/SqlTopicRepository.Save-implicit-IsDirty' into develop

This resolves a bug in which attributes which had been reconfigured from extended to indexed storage weren't being saved by `SqlTopicRepository.Save()` unless the `Topic` was explicitly marked as `IsDirty()`. This fix ensures that topics that are _implicitly_ dirty due to `IsExtendedAttribute` mismatches are treated as `IsDirty()` as far as `Save()` is concerned. This was already supported for indexed attributes configured as extended attributes, but not the other way around.

This resolves Issue #73.

Author: JeremyCaney

OnTopic.Data.Sql/SqlTopicRepository.cs

@@ -373,7 +373,10 @@ bool persistRelationships
       | current command. A more aggressive version of this would wrap much of the below logic in this, but this is just meant
       | as a quick fix to reduce the overhead of recursive saves.
       \-----------------------------------------------------------------------------------------------------------------------*/
-      areAttributesDirty        = areAttributesDirty || extendedAttributeList.Any(a => a.IsExtendedAttribute == false);
+      areAttributesDirty        =
+        areAttributesDirty      ||
+        indexedAttributeList.Any(a => a.IsExtendedAttribute == true) ||
+        extendedAttributeList.Any(a => a.IsExtendedAttribute == false);
 
       var isDirty               =
         isTopicDirty            ||