ci: add wycheproof vector test job

[MarkAtwood]

Summary

• Adds .github/workflows/wycheproof.yml which builds wolfSSL from the PR branch and runs it against the wolfSSL/wychcheck test suite (340+ Wycheproof JSON test files, NIST ACVP vectors, and RFC vectors covering AES-GCM, AES-EAX, AES-SIV, ChaCha20-Poly1305, RSA-PSS, RSA-OAEP, ECDH/ECDSA over all curves, X25519, ML-DSA, ML-KEM, SLH-DSA, EdDSA)
• Guarded with if: github.repository_owner == 'wolfssl' per project convention
• Only inits the wycheproof submodule (not acvp-server which is 900 MB)
• Uploads JUnit XML results as a build artifact

Relationship to wychcheck

wolfSSL/wychcheck already runs nightly against wolfssl/wolfssl master (Saturday 22:00 UTC). This job adds per-PR coverage so regressions are caught before merge rather than after.

Test plan

• Verify job appears in PR checks
• Confirm wolfcrypt-check builds and ctest passes
• Confirm artifact upload contains wycheproof-results/test-results.xml

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Adds a dedicated GitHub Actions workflow to run wolfSSL against the wolfSSL/wychcheck (Wycheproof + vector) suite on pushes and PRs, and to publish JUnit XML results as an artifact.

Changes:

• Introduces .github/workflows/wycheproof.yml with a new wycheproof CI job.
• Builds wolfSSL from the PR branch, builds wolfcrypt-check from wolfSSL/wychcheck, and executes ctest with JUnit output.
• Uploads the generated JUnit XML as a workflow artifact.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

This workflow assumes build tooling (e.g., autoconf/automake/libtool, compiler toolchain, cmake/ctest) is present on ubuntu-latest. Since ubuntu-latest runner contents can change over time, this can cause sporadic CI failures. Add an explicit dependency-install step (apt-get) before autoreconf/cmake to make the job deterministic.

[MarkAtwood]

@copilot apply changes based on this feedback

[MarkAtwood]

@copilot apply changes based on this feedback

[github-actions]

MemBrowse Memory Report

No memory changes detected for:

• gcc-arm-cortex-m4- gcc-arm-cortex-m4-baremetal- gcc-arm-cortex-m4-min-ecc- gcc-arm-cortex-m4-tls12

[LinuxJedi]

That isn't an option. Did you mean --enable-aeskeywrap?