CVPN-1615 Remove liboqs and use WolfSSL's Kyber implementation

[kp-thomas-yau]

Description

This PR removes liboqs and would instead use WolfSSL's implementation of Kyber. Since WolfSSL would officially release their Kyber/ML-KEM implementations a few months later, we would use the git patch to essentially patch their PRs on top of the 5.7.4 release.

The patch consists of the commits and code changes from the following PR from WolfSSL:

• Kyber/ML-KEM: make both available wolfSSL/wolfssl#8143
• Kyber benchmark: allow ML-KEM and Kyber wolfSSL/wolfssl#8172
• Kyber: fixes to configure and wolfSSL_get_curve_name wolfSSL/wolfssl#8183
• Kyber: Fix wolfSSL_get_curve_name() wolfSSL/wolfssl#8185

Configuration for enabling ML-KEM/Kyber:

1. For only ML-KEM:
   ./configure --enable-kyber
   ./configure --enable-kyber=all,ml-kem
2. For just Kyber:
   ./configure --enable-kyber=all,original
3. For ML-KEM and Kyber
   ./configure --enable-kyber=all,original,ml-kem
   ./configure --enable-kyber=all,ml-kem,original

Motivation and Context

Reduce external dependency, prepare migration to ML-KEM

How Has This Been Tested?

Tested with a UDP xv-helium-server with new lightway-core (aka NO LIBOQS) with

1. xv-helium-cli that has OLD (the first connection) lightway-core WITH Liboqs--> Use Kyber Level 1, expected
2. xv-helium-cli that has NEW (the second connection) lightway-core WITHOUT Liboqs --> Use Kyber Level 5, expected
   

Also tested it with TCP, both uses Kyber level 5 as expected

Passes mac coverage test and other unit tests as well

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• All active GitHub checks are passing
• The correct base branch is being used, if not main

[xv-raihaan-m]

This PR removes liboqs and would instead use WolfSSL's implementation of Kyber. Since WolfSSL would officially release their Kyber/ML-KEM implementations a few months later, we would use the git patch to essentially patch their PRs on top of the 5.7.4 release.

Does this mean the server needs to be rolled out first? i.e iss this change backwards compatible?

[kp-thomas-yau]

This PR removes liboqs and would instead use WolfSSL's implementation of Kyber. Since WolfSSL would officially release their Kyber/ML-KEM implementations a few months later, we would use the git patch to essentially patch their PRs on top of the 5.7.4 release.

Does this mean the server needs to be rolled out first? i.e iss this change backwards compatible?

We will update the server first so that it can support older/new client as well. We would only update the clients after the server slowly rolls out.