Also assert that targets of an L2XC do not have an address or LCP

unittest/error-l2xc4.yaml

@@ -2,9 +2,11 @@ test:
   description: "L2 cross connect targets cannot have an IP address or LCP"
   errors:
     expected:
-     - "interface .* l2xc so it cannot be an LCP"
-     - "interface .* l2xc so it cannot have an address"
-    count: 3
+     - "interface .* has l2xc so it cannot be an LCP"
+     - "interface .* has l2xc so it cannot have an address"
+     - "interface .* l2xc target .* cannot be an LCP"
+     - "interface .* l2xc target .* cannot have an address"
+    count: 6
 ---
 interfaces:
   GigabitEthernet1/0/0:

unittest/error-l2xc5.yaml

@@ -2,7 +2,7 @@ test:
   description: "L2 cross connect from a phy cannot also have sub-interfaces"
   errors:
     expected:
-     - "interface .* l2xc so it cannot have sub-interfaces"
+     - "interface .* has l2xc so it cannot have sub-interfaces"
     count: 1
 ---
 interfaces:

unittest/error-l2xc6.yaml

@@ -0,0 +1,23 @@
+test:
+  description: "L2 cross connect target cannot have an IP address or LCP"
+  errors:
+    expected:
+     - "sub-interface .* l2xc target .* cannot have an address"
+     - "sub-interface .* l2xc target .* cannot be an LCP"
+    count: 2
+---
+interfaces:
+  GigabitEthernet1/0/0:
+    sub-interfaces:
+      100:
+        l2xc: GigabitEthernet1/0/1.100
+      200:
+        l2xc: GigabitEthernet1/0/1.200
+
+  GigabitEthernet1/0/1:
+    lcp: "xe1-0-1"
+    sub-interfaces:
+      100:
+        addresses: [ 192.0.2.1/30 ]
+      200:
+        lcp: 'foo'