API Perf improvement and Fish cpu/mem limitations

[sparshev]

Found that due to really tough Argon2 configurations we spend enormous amount of time/memory in user password hash validation. According to the last tests that could be a reason for OOMs in #64.

• Re-balanced parameters of Argon2 hashing so it's executing much faster, but needs regeneration of passwords for the existing users - for skipped users the API performance will stay the same.
• Added a number of tests & benchmarks to prevent the further degradation.
• Added CPU limit & RAM target to keep OOM from happening.

Related Issue

fixes: #64

Motivation and Context

How Has This Been Tested?

Automatically & Manually on prev version to ensure safe upgrade

Types of changes

• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• [x] I have signed the Adobe Open Source CLA.
• [x] My code follows the code style of this project.
• [x] My change requires a change to the documentation.
• [x] I have updated the documentation accordingly.
• [x] I have read the CONTRIBUTING document.
• [x] I have added tests to cover my changes.
• [x] All new and existing tests passed.