Move password check logic to client + automatically show #85
Description
What needs refactoring?
The password checking in register and reset-password.
Why?
Currently, the logic is such that the backend API is called to check if the password is strong enough. To reduce the number of API calls, this is only done after a certain amount of inactivity time, resulting in a delayed response on the user's input.
Instead, it would make sense to have the password strength logic purely on the client. This will result in more immediate feedback.
For reference, the password strength requirements can be found here.
Also, the password strength criteria should be shown as soon as the password field is focused.
You should edit the PasswordCriteria component to accomplish this, and add a message for when the password is strong enough.