add event seeding file for populating home page with test events

[TVW96]

Summary & Changes 📃

• Resolves: Issue: Missing EventsData and UserData – Add Database Seed File #175

Changes made:

• Added: scripts/events-seed.js
• Added: scripts/users-seed.js
• Added: command for running scripts in package file.
• Added: logic for global-teardown.ts.
• Updated: test to include removal of test users and test events after test completed. This process is again repeated when running the global-teardown file.

_{📌 Required for: UI changes, layout updates, or bug fixes.}

Expand ⬇️

---

How to Test 🧪

Step 1: Run the setup script in your terminal

linux:

bash setup-macos-linux.sh

windows:

bash setup-windows.bat

Step 2: Start the project by running this command in terminal: npm run dev.
Step 3: Run this new seed command to populate database with visible test events npm run seed.

---

Expected Behavior: (Describe what should happen)

Event data is visible when navigating webpage.

Checklist ✅

• I have tested this PR locally and it works as expected.
• This PR resolves an issue (Resolves #issue-number).
• Reviewers, assignees(self), tags, and labels are correctly assigned.
• Squash commits and enable auto-merge if approved.

[github-actions]

✅ Full E2E Test Results

Running full test suite (critical files changed)

Status	Count
✅ Passed	47
❌ Failed	0
📊 Total	47

View detailed report

[IsaacJrTypes]

Hi Troy! Thanks for taking initiative and creating the issue: #175 . I agree that there needs to be a seed file to help developers when testing the repo locally. There is a concern I have with seeding the database through an API endpoint.

Concern

• If one runs the seeding scripts twice, we will get duplicate events for testing which might confuse some developers.

Is your end goal to seed the database through the API endpoint to actually provide a postgres seed file?
If so, I am assuming that there will be follow up PRs that will generate said postgres seed and schema files.

Another way to insert new data to a database is to connect to the database instance, using pgadmin or datagrip, and write insert postgres sql scripts.

It is ideal for developers to seed the database directly through postgres dump like files.

Links to other projects that take this approach

• SQL seed file
• SQL schema file
• Insert data example
• Look at the screenshot section of this PR for hints on connecting datagrip to local database instance

If you do plan on creating dump like sql files, let me know and I will approve so this PR doesn't become a blocker