Fix X.509 parsing to support PQC use in attestation statements (#800)

This PR updates dependencies and maps PQC X.509 algorithm OIDs so that
attestation statements leveraging PQC algorithms can be properly
verified.

Note that I still cannot yet include full registration responses
containing PQC-using attestation statements as test vectors because I am
under an NDA.

This PR also includes some intentional raising of a new
`PQCNotSupportedError` when verifying responses with PQC passkeys in
runtimes that don't support PQC. This happens earlier in the flow so
that downstream problems that happen because of the lack of PQC support
are't masked as other types of errors.

And I also included some test optimizations.

Fixes #799

Author: MasterKale

deno.lock

@@ -36,6 +36,7 @@
     "lineWidth": 100
   },
   "imports": {
+    "reflect-metadata": "npm:reflect-metadata@^0.2.2",
     "tiny-cbor": "npm:@levischuck/tiny-cbor@^0.2.2",
     "@hexagon/base64": "npm:@hexagon/base64@^1.1.27",
     "@levischuck/tiny-cbor": "npm:@levischuck/tiny-cbor@^0.2.2",
@@ -44,7 +45,8 @@
     "@peculiar/asn1-rsa": "npm:@peculiar/asn1-rsa@^2.6.1",
     "@peculiar/asn1-schema": "npm:@peculiar/asn1-schema@^2.6.0",
     "@peculiar/asn1-x509": "npm:@peculiar/asn1-x509@^2.6.1",
-    "@peculiar/x509": "npm:@peculiar/x509@^1.14.3"
+    "@peculiar/asn1-x509-post-quantum": "npm:@peculiar/asn1-x509-post-quantum@^2.9.4",
+    "@peculiar/x509": "npm:@peculiar/x509@^2.1.0"
   },
   "publish": {
     "include": [