Updated ChunkingTests_Literalization_with_BT_Constraints2_expected to…

… not redundantly test the same object1 twice. it seems like this is another case where maybe the default to have singletons leads to a more correct chunk, but I'm not certain.

UnitTests/SoarTestAgents/Chunking/expected/ChunkingTests_Literalization_with_BT_Constraints2_expected.soar

@@ -1,14 +1,14 @@
 sp {answer*start-chunking*StateNoChange*t2-2
-    (state <s1> ^object1 object ^superstate nil ^object2 <c2> ^object1 <c1>)
+    (state <s1> ^object1 object ^superstate nil ^object2 <c2>)# ^object1 <c1>)
     -->
-    (<s1> ^result1u ungrounded + ^result1b <c2> + ^result1c <c1> +)
+    (<s1> ^result1u ungrounded + ^result1b <c2> + ^result1c object +)
 }
 
 sp {answer*start-chunking-partial-lit*StateNoChange*t2-1
-    (state <s1> ^superstate nil ^object2 <c3> ^object1 <c2>
+    (state <s1> ^superstate nil ^object2 <c3> #^object1 <c2>
           ^object1 { >= <c1> <c1> })
     -->
-    (<s1> ^result2a ungrounded + ^result2b <c3> + ^result2c <c2> +)
+    (<s1> ^result2a ungrounded + ^result2b <c3> + ^result2c <c1> +)
 }