feat: data faker

[aruaycodes]

Description

closes #15 Added a fakerjs that creates 10 fake user data when running:

bun db:seed

---

PR Checklist (Please do not remove)

• [x] Read the CONTRIBUTING guide
• [ ] Title this PR according to the type(scope): description or type: description format
• [ ] Provide description sufficient to understand the changes introduced in this PR, and, if necessary, some screenshots
• [ ] Reference an issue or discussion where the feature or changes have been previously discussed
• [ ] Add a failing test that passes with the changes introduced in this PR, or explain why it's not feasible
• [ ] Add documentation for the feature or changes introduced in this PR to the docs; you can run them with bun docs

[yamcodes]

@aruay99, thank you so much for the contribution.

1. As a convention, I've edited your title from feat: added data faker to feat: data faker. The the AngularJS Git Commit Guidelines linked in our CONTRIBUTING.md states:

   Subject

   The subject contains succinct description of the change:

   • use the imperative, present tense: "change" not "changed" nor "changes"
   • don't capitalize first letter
   • no dot (.) at the end

2. Kindly make sure to handle all items on the checklist in your next PR. This helps us ensure code quality and convention and removes friction.

[yamcodes]

I'm testing this PR locally, ideally seed should be idempotent, which means that if it's ran on every boot of the container we shouldn't create new users.

A potential fix is to truncate the affected table before inserting, which will ensure in this case there is exactly 10 users after every seed.

In that case, we can remove the onConflictDoNothing() statement here which will become uneccesary.