fix(argond2id):reordering parameters order during serialization to ma…

[Benjamin-htr]

…tch phc standard

🔗 Linked issue

#12

❓ Type of change

• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Resolves #12

Reordeing parameters order of argon2id hash during serialization process to match this line of phc standard :
"The parameters shall appear in the m,t,p,keyid,data order."
https://github.com/P-H-C/phc-string-format/blob/master/phc-sf-spec.md

and to resolve compatibility issue with other tools described on the above issue

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

Tests

All tests passed

[RomainLanz]

Hey @Benjamin-htr! 👋🏻

Just to clarify — are you saying our package doesn't recognize other hashes, or that the other tool can't read our hash?

Since the parameters are handled as an object, their order shouldn't matter.

[Benjamin-htr]

Other tools are not able to validate adonisjs/hash generated hashs because of the parameters order

[thetutlage]

Just to make sure we are not breaking old hashes. Can you please add a test that has assertions on a pre-computed hash with wrong and the right order.

[thetutlage]

Thanks 👍