Update KDE vault needles and test

The backend is now cryfs in F36/Rawhide. I don't think we need
to be policing which backend Vault decides to use, so let's just
accept either.

Signed-off-by: Adam Williamson <awilliam@redhat.com>

needles/kde/apps/vault/vault_backend_available-cryfs-20220303.json

@@ -0,0 +1,15 @@
+{
+  "area": [
+    {
+      "xpos": 203,
+      "width": 103,
+      "type": "match",
+      "height": 20,
+      "ypos": 183
+    }
+  ],
+  "properties": [],
+  "tags": [
+    "vault_backend_available"
+  ]
+}

needles/kde/apps/vault/vault_backend_available-encfs.json

@@ -1,7 +1,7 @@
 {
   "properties": [],
   "tags": [
-    "vault_encfs_backend_available"
+    "vault_backend_available"
   ],
   "area": [
     {
@@ -12,4 +12,4 @@
       "type": "match"
     }
   ]
-}
+}

needles/kde/apps/vault/vault_menu_create_new-20220303.json

@@ -0,0 +1,15 @@
+{
+  "area": [
+    {
+      "width": 148,
+      "xpos": 721,
+      "height": 16,
+      "ypos": 533,
+      "type": "match"
+    }
+  ],
+  "properties": [],
+  "tags": [
+    "vault_menu_create_new"
+  ]
+}

tests/apps_startstop/kde/vault.pm

@@ -26,7 +26,7 @@ sub run {
     assert_screen "vault_dialog_runs";
 
     # Check that a correct backend is available
-    assert_screen "vault_encfs_backend_available";
+    assert_screen "vault_backend_available";
 
     # Enter the name of the newly created testvault
     assert_and_click "vault_enter_name";