Set ML-KEM alg_version to "FIPS203"

[SWilson4]

To bring ML-KEM in line with the upcoming ML-DSA update.

Fixes #1996

• 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.)

[baentsch]

Pretty massive changes for 3 lines of code... Ideas why this is so?

[SWilson4]

Pretty massive changes for 3 lines of code... Ideas why this is so?

I did wonder about this also. I generated the patch using git diff-tree as documented here. It looks to me as if the original patch was generated with git diff—when I update the patch using git diff the diff (of the diff) is much smaller, as I would have expected.

I'm fine to update the patch with git diff instead to make the changes easier to view.

[bhess]

Thanks @SWilson4 for updating this! You're right, the original patch was made with git diff.

[dstebila]

Looking for one more review @open-quantum-safe/liboqs-committers

[Martyrshot]

LGTM!