itest: Add required disconnect in revoke test

This adds a disconnection between nodes in the
testRevokedCloseRetributionZeroValueRemoteOutput integration test.

This disconnection is necessary to ensure the nodes don't reconnect upon
restarting and disable the channel used for retribution tests.

Author: matheusd

lnd_test.go

@@ -6726,7 +6726,10 @@ func testRevokedCloseRetributionZeroValueRemoteOutput(net *lntest.NetworkHarness
 	// protection logic automatically.
 	dave, err := net.NewNode(
 		"Dave",
-		[]string{"--debughtlc", "--hodl.exit-settle", "--nolisten"},
+		[]string{
+			"--debughtlc", "--hodl.exit-settle", "--nolisten",
+			"--unsafe-disconnect",
+		},
 	)
 	if err != nil {
 		t.Fatalf("unable to create new node: %v", err)
@@ -6824,6 +6827,14 @@ func testRevokedCloseRetributionZeroValueRemoteOutput(net *lntest.NetworkHarness
 		t.Fatalf("unable to get carol chan info: %v", err)
 	}
 
+	// Disconnect Dave from Carol, so that upon Carol's restart he doesn't
+	// try to automatically reconnect and alert her of the changed state.
+	ctxt, _ = context.WithTimeout(ctxb, defaultTimeout)
+	err = net.DisconnectNodes(ctxt, dave, carol)
+	if err != nil {
+		t.Fatalf("unable to disconnect dave and carol: %v", err)
+	}
+
 	// Now we shutdown Carol, copying over the his temporary database state
 	// which has the *prior* channel state over his current most up to date
 	// state. With this, we essentially force Carol to travel back in time