fix(challenges): fix description and tests to use sync hashing

[ivan3123708]

ISSUES CLOSED: #119

Description

Changed challenge description for password hashing code to use sync method because previous one used async code but didn't handle it correctly.

Pre-Submission Checklist

• Your pull request targets the dev branch.
• Branch starts with either fix/, feature/, or translate/ (e.g. fix/challenge-tests)
• All new and existing tests pass the command npm test.
• Use npm run commit to generate a conventional commit message.
  Learn more here: https://conventionalcommits.org/#why-use-conventional-commits
• The changes were done locally on your machine and NOT GitHub web interface.
  If they were done on the web interface you have ensured that you are creating conventional commit messages.

Checklist:

• Tested changes locally.
• Addressed currently open issue (replace XXXXX with an issue no in next line)

Closes #119

[scissorsneedfoodtoo]

👍 Awesome! Everything LGTM 👍

Thank you for taking the time to report and creating a PR to fix this issue, @ivan3123708. Looking forward to your next contribution.