Feature/client password hashing

[evilaliv3]

This pull requests moves password hashing on with the following properties:

• Key derivation is now performed on the client with 16 steps and memory requirement set to 128MB
• The backend will preserve a sha512 hash of the key in order to perform authentication
• Users with a previous configuration will be able to perform a first login supported by the backend and automatically will transition into client hashing mode after their first password change
• Whistleblowers of an existent system with existing will continue to need to be supported by the backend with backend key derivation for old and new report; New systems, systems with no reports or systems where every existing reports expire will automatically start using client key derivation
• proof of work has been re-implemented replacing sha256 with argon2id with 1 iteration and 1MB of RAM requirement;
• python base64 encoding has been replaced with nacl.encoding.Base64Encoder preferring usage of functions designed in the context of cryptographic applications

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
❌ -12.10% (target: -0.10%)	✅ 79.58% (target: 70.00%)

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (2a1a9ec)	19234	16089	83.65%
Head commit (ffc853b)	43590 (+24356)	31186 (+15097)	71.54% (-12.10%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#4375)	480	382	79.58%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

_{Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more}

[evilaliv3]

@msmannan00 : when you like please feel free to proceed with the review of this pull request as well! thank you