Fix Use of password hash with insufficient computational effort

[gitworkflows]

Category:

One of: Bugfix / Feature / Code style update / Refactoring Only / Build related changes / Documentation / Other (please specify)

Overview
To fix the problem, we need to replace the use of sha256 with a more secure password hashing algorithm, such as bcrypt. This will ensure that the hashed passwords are computationally intensive to crack, providing better security.

1. Import the bcrypt library.
2. Replace the makeSubHash function to use bcrypt for hashing the password.
3. Ensure that the bcrypt hash is truncated to the same length (14 characters) to maintain existing functionality.

Issue Number (if applicable) #00

New Vars (if applicable)

If you've added any new build scripts, environmental variables, config file options, dependency or devDependency, please outline here

Screenshot (if applicable)

If you've introduced any significant UI changes, please include a screenshot

Code Quality Checklist (Please complete)

• [*] All changes are backwards compatible
• [*] All lint checks and tests are passing
• There are no (new) build warnings or errors
• (If a new config option is added) Attribute is outlined in the schema and documented
• (If a new dependency is added) Package is essential, and has been checked out for security or performance
• (If significant change) Bumps version in package.json

[netlify]

❌ Deploy Preview for dashy-dev failed. Why did it fail? →

Name	Link
🔨 Latest commit	527c12a
🔍 Latest deploy log	https://app.netlify.com/sites/dashy-dev/deploys/671891f6a698570008da33b5