Avoid the "gets or sets" verbiage for records

Records are immutable, so while their properties can be set during initialization, they'll be in a read-only state for most developers. Given that, prefer just "gets" over "gets or sets". (This could, alternatively, use the more accurate "gets or initializes".)

Author: JeremyCaney

OnTopic.ViewModels/BindingModels/AssociatedTopicBindingModel.cs

@@ -27,7 +27,7 @@ public record AssociatedTopicBindingModel : IAssociatedTopicBindingModel {
     | PROPERTY: UNIQUE KEY
     \-------------------------------------------------------------------------------------------------------------------------*/
     /// <summary>
-    ///   Gets or sets the topic's <see cref="UniqueKey"/> attribute, the unique text identifier for the topic.
+    ///   Gets the topic's <see cref="UniqueKey"/> attribute, the unique text identifier for the topic.
     /// </summary>
     /// <requires description="The value from the getter must not be null." exception="T:System.ArgumentNullException">
     ///   value is not null