Add validation when a password is generated

[EMaksy]

Description

This pr aims to improve the password generation in order to support our password rules, as the current implementation has a very unlikely case not to meet the requirements.

Password Rules:

• at least have 8 characters --> added validation to check for minimum length
• does not have 3 consecutive repeated numbers or letters (example: 111 or aaa) --> added validation for repetitive chars by using a regex rule, which checks for any character that appears three or more times consecutively in a string.
• does not have 3 consecutive sequential numbers or letters (example: 123 or abc) --> added ASCII code validation for sequence of chars ascending and descending, exluding special chars to allow combinations like 89: or yz{

Also, this pr will ensure the unlikely case that e2e test fail if the generated password does not meet the requirements
It is a follow-up to @rtorrero comment: #2576 (comment)

How was this tested?

Added test for validation functions

[arbulu89]

Hey @EMaksy
Some comments.

• I wouldn't export all the auxiliary functions. Just create a isValidPassword or similar, which includes all the other sub functions. And you can test this with all the cases.

• The sequential test looks complex. I would try to get inspiration in the code we have in the backend. It looks simpler: https://github.com/trento-project/web/blob/user_management/lib/trento/users/user.ex#L120

[arbulu89]

Really good!
Some comments in the tests, but good to go

[arbulu89]

I would put some new lines between describe and test entries