nixguix: Exclude faulty "recursive" file origins from listing

For now, those can be faulty as the manifest is missing 'critical' information about how to recompute the hash (e.g. fs layout, executable bit, ...).

The problem has been reported upstream [1]. In the meantime, this looks like a good way to avoid injecting noise within the archive.

• [1] Related to T4608 Related to T3781

---

Migrated from D8637 (view on Phabricator)

swh/lister/nixguix/tests/data/sources-failure.json

@@ -37,6 +37,17 @@
       ],
       "inferredFetcher": "fetchzip"
     },
+    {
+      "outputHash": "0s2mvy1nr2v1x0rr1fxlsv8ly1vyf9978rb4hwry5vnr678ls522",
+      "outputHashAlgo": "sha256",
+      "outputHashMode": "recursive",
+      "type": "url",
+      "urls": [
+        "https://www.unicode.org/Public/emoji/12.1/emoji-zwj-sequences.txt"
+      ],
+      "integrity": "sha256-QhRN0THZ7uIzh2RldFJyfgdP0da0u5Az6GGLbIPfVWg=",
+      "inferredFetcher": "unclassified"
+    },
     {
       "type": "url",
       "urls": [ "unknown://example.org/wrong-scheme-so-skipped.txt" ],