Update the test vectors and encoded hash

[samuel-lucas6]

Once the design has been finalised, these need to be updated since breaking changes have been made.

[samuel-lucas6]

List of hash functions/XOFs to consider including test vectors for, with the ones to probably skip crossed out:

1. BLAKE2s-256
2. BLAKE2b-256
3. BLAKE2b-512
4. BLAKE2X
5. BLAKE3 (256 bit output or XOF, not both)
6. SHA-224
7. SHA-256
8. SHA-384
9. SHA-512
10. HMAC-SHA256
11. HMAC-SHA384
12. HMAC-SHA512
13. SHA3-224
14. SHA3-256
15. SHA3-384
16. SHA3-512
17. KMAC128
18. KMAC256
19. KMACXOF128
20. KMACXOF256
21. SHAKE128
22. SHAKE256
23. cSHAKE128
24. cSHAKE256
25. TurboSHAKE128
26. TurboSHAKE256
27. KangarooTwelve
28. MarsupilamiFourteen

That's still over 10 algorithms... Got to hate how many variants there are.

[jedisct1]

27. KangarooTwelve

Given that the inputs are very short, KT12 wouldn't have any advantage over TurboSHAKE, only overhead.

[samuel-lucas6]

Given that the inputs are very short, KT12 wouldn't have any advantage over TurboSHAKE, only overhead.

Thank you for this point. I haven't looked into either and didn't realise there are also two KangarooTwelve variants, so TurboSHAKE or skipping them both would be best.