feat: generate credentials using crypto.random for less collisions

[scheidtdav]

Type of Change

• Dependency upgrade
• Bug fix (non-breaking change)
• Breaking change
  • e.g. a fixed bug or new feature that may break something else
• New feature
• Code quality improvements
  • e.g. refactoring, documentation, tests, tooling, ...

Implementation

All occurences of hard coded credentials for test users in the unit tests have been replaced by a method that implements randomized credentials.
This is using crypto (mostly randomBytes but also randomUUID) to generate the credentials. The rest is still handled by the tests themselves.

I was facing collisions sometimes and was running out of names to name my test users. This solution helps with my lack of fantasy :-)

Checklist

• I gave this pull request a meaningful title
• My pull request is targeting the dev branch
• I have added documentation to my code
• I have deleted code that I have commented out

Additional Information

A lot of the files show a bunch of whitespace changes due to not all files being formatted according to the prettier rules of the project. This was kept to eventually have all files follow the prettier rules in place.

• This PR closes #