[2879] adjusted lettuce tests that are affected by the fix of the branch.

note: this is not a regression.  the original expected value has never made
sense, so this is actually a "correction".  in fact, we should have noticed
the bug of this ticket when we noticed notifyoutv6 was counted 5 times even
it should be a successful notify response.

tests/lettuce/features/xfrin_notify_handling.feature

@@ -81,8 +81,8 @@ Feature: Xfrin incoming notify handling
     last bindctl output should not contain "error"
     Then the statistics counter notifyoutv4 for the zone _SERVER_ should be 0
     Then the statistics counter notifyoutv4 for the zone example.org. should be 0
-    Then the statistics counter notifyoutv6 for the zone _SERVER_ should be 5
-    Then the statistics counter notifyoutv6 for the zone example.org. should be 5
+    Then the statistics counter notifyoutv6 for the zone _SERVER_ should be 1
+    Then the statistics counter notifyoutv6 for the zone example.org. should be 1
     Then the statistics counter xfrrej for the zone _SERVER_ should be 0
     Then the statistics counter xfrrej for the zone example.org. should be 0
     Then the statistics counter xfrreqdone for the zone _SERVER_ should be 1
@@ -184,8 +184,8 @@ Feature: Xfrin incoming notify handling
     last bindctl output should not contain "error"
     Then the statistics counter notifyoutv4 for the zone _SERVER_ should be 0
     Then the statistics counter notifyoutv4 for the zone example.org. should be 0
-    Then the statistics counter notifyoutv6 for the zone _SERVER_ should be 5
-    Then the statistics counter notifyoutv6 for the zone example.org. should be 5
+    Then the statistics counter notifyoutv6 for the zone _SERVER_ should be 1
+    Then the statistics counter notifyoutv6 for the zone example.org. should be 1
     # The counts of rejection would be between 1 and 2. They are not
     # fixed. It would depend on timing or the platform.
     Then the statistics counter xfrrej for the zone _SERVER_ should be greater than 0