Add HMAC-BLAKE2b and HMAC-BLAKE2s API functions

[holtrop-wolfssl]

Description

Add HMAC-BLAKE2b and HMAC-BLAKE2s API functions

Testing

Added unit tests with two KAT vectors for each HMAC-BLAKE2b and HMAC-BLAKE2s. Verified KAT vectors with both OpenSSL and Rust blake2 crate.

Checklist

• added tests
• updated/added doxygen
• updated appropriate READMEs
• Updated manual and documentation

[holtrop-wolfssl]

retest this please (org.jenkinsci.plugins.workflow.support.steps.AgentOfflineException: Unable to create live FilePath for wolf-linux-cloud-node-02zun3; wolf-linux-cloud-node-02zun3 was marked offline: Connection was broken)

[devin-ai-integration]

🛟 Devin Lifeguard found 2 likely issues in this PR

• use-forcezero snippet snippet: Replace both XMEMSET(x_key, 0, BLAKE2B_BLOCKBYTES); / XMEMSET(i_hash, 0, BLAKE2B_OUTBYTES); (and the corresponding BLAKE2s lines) with ForceZero(x_key, BLAKE2B_BLOCKBYTES); and ForceZero(i_hash, BLAKE2B_OUTBYTES);.
• limit-stack-usage snippet snippet: Move x_key and i_hash (and optionally the state) to heap-allocated buffers using the WOLFSSL_SMALL_STACK pattern (e.g., XMALLOC / XFREE) to keep per-call stack usage under 100 bytes.

@holtrop-wolfssl
please take a look at the above issues which Devin flagged. Devin will not fix these issues automatically.

[holtrop-wolfssl]

🛟 Devin Lifeguard found 2 likely issues in this PR

• use-forcezero snippet snippet: Replace both XMEMSET(x_key, 0, BLAKE2B_BLOCKBYTES); / XMEMSET(i_hash, 0, BLAKE2B_OUTBYTES); (and the corresponding BLAKE2s lines) with ForceZero(x_key, BLAKE2B_BLOCKBYTES); and ForceZero(i_hash, BLAKE2B_OUTBYTES);.
• limit-stack-usage snippet snippet: Move x_key and i_hash (and optionally the state) to heap-allocated buffers using the WOLFSSL_SMALL_STACK pattern (e.g., XMALLOC / XFREE) to keep per-call stack usage under 100 bytes.

@holtrop-wolfssl please take a look at the above issues which Devin flagged. Devin will not fix these issues automatically.

@douzzer / @SparkiDev - I had mostly copied and adapted @douzzer's kernel implementation for this. But would it make sense to you two to fix either/both of these Devin suggestions?

[devin-ai-integration]

🛟 Devin Lifeguard found 2 likely issues in this PR

• use-forcezero snippet snippet: Insert ForceZero(x_key, sizeof(x_key)); just before the return ret; statement in both wc_Blake2bHmacFinal() and wc_Blake2sHmacFinal() to securely clear the key material.
• limit-stack-usage snippet snippet: Move the 128-byte x_key buffers and the Blake2b state struct in wc_Blake2bHmacInit/Final and wc_Blake2bHmac to heap memory using the WOLFSSL_SMALL_STACK pattern (e.g., #ifdef WOLFSSL_SMALL_STACK byte* x_key = (byte*)XMALLOC(BLAKE2B_BLOCKBYTES, heap, DYNAMIC_TYPE_TMP_BUFFER); and XFREE() before return).

@holtrop-wolfssl
please take a look at the above issues which Devin flagged. Devin will not fix these issues automatically.

[SparkiDev]

The convention is * .
Also the convention in the file.

[holtrop-wolfssl]

What does "The convention is * ." mean? Are you asking for the space character before the "*" to be removed?

[SparkiDev]

Sorry the important text got lost in the markup:

The convention is <type>* <name>.
Also the convention in the file.

[holtrop-wolfssl]

Got it. Ok, I will switch those. Should I also change the wc_InitBlake2b_WithKey() key parameter to match this as well for consistency or is it frowned upon to make stylistic-only changes to other preexisting lines?