PQC enforce modulus and eta range checks in DecodePrivateKey

[aidangarske]

Description

• In Add ML-KEM and ML-DSA support wolfProvider#399 I did inter-op test with WP and openssl. There wherre 2 issues with mlkem and mldsa
• 1. mlkem specifically needed A modulus check needed to be added to reject non reduced priv key vectors on decode
• 2. mldsa needs to reject priv key data with out of range s1/s2
• Added neg test vectors to fix
• Tested in WP 2602 interop pass from openssl test suite
• skoll, copilot, fenrir addressed

[Frauschi]

LGTM, but @SparkiDev should give the final go on this.

[github-actions]

retest this please

[github-actions]

MemBrowse Memory Report

gcc-arm-cortex-m4-pq

• FLASH: .text +128 B (+0.0%, 277,656 B / 1,048,576 B, total: 26% used)

gcc-arm-cortex-m7-pq

• FLASH: .text +128 B (+0.0%, 278,296 B / 1,048,576 B, total: 27% used)

linuxkm-pie

• Data: __patchable_function_entries +8 B (+0.0%, 24,272 B)

linuxkm-standard

• Data: __patchable_function_entries +8 B (+0.0%, 45,968 B)
  No memory changes detected for:
• gcc-arm-cortex-m0plus
• gcc-arm-cortex-m3
• gcc-arm-cortex-m4
• gcc-arm-cortex-m4-baremetal
• gcc-arm-cortex-m4-crypto-only
• gcc-arm-cortex-m4-dtls13
• gcc-arm-cortex-m4-min-ecc
• gcc-arm-cortex-m4-openssl-compat
• gcc-arm-cortex-m4-pkcs7
• gcc-arm-cortex-m4-rsa-only
• gcc-arm-cortex-m4-sp-math
• gcc-arm-cortex-m4-tls12
• gcc-arm-cortex-m4-tls13
• gcc-arm-cortex-m7
• gcc-arm-cortex-m7-tls13
• stm32-sim-stm32h753

[ColtonWilley]

Jenkins retest this please

[SparkiDev]

Private values should come from a trusted source but having the check won't hurt.