fix(e2e): assert DNSRecordSet conditions order-independently

The DNSRecordSet emits conditions as [Programmed, Accepted]; chainsaw
matches bare lists positionally, so the [Accepted, Programmed] assertion
failed. Use JMESPath filters per condition type.

Refs #46

Author: kevwilliams

test/e2e/display-annotations/chainsaw-test.yaml

@@ -178,12 +178,14 @@ spec:
           kind: DNSRecordSet
           metadata:
             name: www-annotations-test
+          # Assert both conditions are True without depending on their order in
+          # the slice (chainsaw matches bare lists positionally; the DNSRecordSet
+          # emits them as [Programmed, Accepted]).
           status:
-            conditions:
-            - type: Accepted
-              status: "True"
-            - type: Programmed
-              status: "True"
+            (conditions[?type == 'Accepted']):
+            - status: "True"
+            (conditions[?type == 'Programmed']):
+            - status: "True"
 
   - name: Teardown - delete resources
     try: