core/crypto: Test against test vectors from wycheproof

[Yawning]

While core/crypto has test cases lifted from various sources, there is always room for improvement, and testing the various primitives against the test vectors from the wycheproof collection would be nice to have, especially to catch the extremely subtle implementation errors, and edge-cases that are possible in the harder to implement primitives (ECC, RSA, etc).

I was/will probably do this at some point, but my bandwidth is limited, and this would be a good first project for someone.

• Pull the relevant test vectors via tests/core/download_assets.py
• Add something like test/core/crypto/test_crypto_wycheproof.odin that parses the JSON files, and runs the tests
• (Hopefully everything in core/crypto will pass now, but) Fix issues that are found

If someone wants to tackle this before I get to it, please ask me questions about it if any arise.

[Yawning]

I'm slowly working on this in a private repo.

• [x] Define the schemas, load/unmarshal
• [x] Cover all the algorithms that are possible
  • [x] chacha20poly1305
  • [x] HKDF
  • [x] HMAC
  • [x] KMAC
  • [x] PBKDF2
  • [x] Ed25519
  • [x] X25519
  • [x] SipHash

Unfortunately BLAKE2, MD5, Keccak, and TupleHash don't have wycheproof artifacts, but I'm largely interested in this for ECC, AES, RSA.

[Yawning]

This covers everything currently in core/crypto that has corresponding wycheproof test cases:

• https://github.com/yawning/odin-wycheproof

Notes:

• Cases that I know will panic are skipped (I could test the panic case by forking on Unix systems as a future improvement).
• The large iteration PBKDF2-HMACSHA1 test is skipped as it takes an unreasonable amount of time (~106s default/no optimization, ~8s with optimization), and I kept forgetting to add -o:speed when building.

[Yawning]

The corpus of test vectors is rather large, and I wrote this as a stand-alone executable rather than using core:testing (which can be changed), so this could be ran from a CI workflow so that people aren't forced to checkout the test vector repo.

The compiler also intermittently segfaulted when building the binary, but short of "it happened, but when I re-ran the build" I don't have futher information.