Update mldsa-native to v1.0.0-beta [full tests] [extended tests]

[mkannwischer]

mldsa-native v1.0.0-beta has just been released. We intend to publish more regular releases (every 2-3 months) from now on, so releases may not have a well defined set of completed features.
Please let me know if you would like me to open a PR into liboqs after each release or if you would like to be more selective.

This should also unblock #2366.

• Does this PR change the input/output behaviour of a cryptographic algorithm (i.e., does it change known answer test values)? (If so, a version bump will be required from x.y.z to x.(y+1).0.)
• Does this PR change the list of algorithms available -- either adding, removing, or renaming? Does this PR otherwise change an API? (If so, PRs in fully supported downstream projects dependent on these, i.e., oqs-provider will also need to be ready for review and merge by the time this is merged. Also, make sure to update the list of algorithms in the continuous benchmarking files: .github/workflows/kem-bench.yml and sig-bench.yml)

[mkannwischer]

The Wycheproof CI failures look unrelated to my changes to me, but instead related to the problems addressed by #2387.

[bhess]

Thanks for the PR, @mkannwischer, updating mlkem-native.

I believe that #2393 should address the failing CI by pinning the Wycheproof tests to a known passing state. Do you want to rebase this PR now that #2393 has been merged?

Please let me know if you would like me to open a PR into liboqs after each release or if you would like to be more selective.

We briefly discussed this in today’s TSC meeting, having PRs after each release would be great. Thanks for being proactive about this!

[mkannwischer]

Thanks for the PR, @mkannwischer, updating mlkem-native.

I believe that #2393 should address the failing CI by pinning the Wycheproof tests to a known passing state. Do you want to rebase this PR now that #2393 has been merged?

Thanks for the ping! Rebased.

Please let me know if you would like me to open a PR into liboqs after each release or if you would like to be more selective.

We briefly discussed this in today’s TSC meeting, having PRs after each release would be great. Thanks for being proactive about this!

Okay, will do. Next will be a mlkem-native release some time in May - hopefully with the ppc backend.

[bhess]

Thanks @mkannwischer. Looks good to me! I'll approve once you mark it ready for review.