feature/get-all-activity-logs

[mdawoud27]

PR Checklist (required)

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines.

• Tests for the changes have been added (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation changes
• Other... Please describe:

Related Issue

Closes #183

[Copilot]

Pull Request Overview

This PR introduces a new feature to retrieve all activity logs for an organization. Key changes include:

• Renaming the password field to newPassword in the reset password validation.
• Adding a new route and controller for fetching activity logs.
• Updating activity log creation in the authentication controller and documenting the new endpoint in the README.

Reviewed Changes

Copilot reviewed 27 out of 30 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
src/validations/auth.validations.js	Updated field name to align with reset password schema requirements.
src/routes/activitylog.routes.js	Added a new route to handle activity logs fetching.
src/index.js	Integrated the new activity log route into the application.
src/controllers/auth.controller.js	Updated activity log details and changed user id reference in logout.
src/controllers/activitylog.controller.js	Implemented the controller to fetch and paginate activity logs.
README.md	Documented the new endpoint for retrieving activity logs.

Files not reviewed (3)

• prisma/migrations/20250419103629_add_cascade_delete_to_user/migration.sql: Language not supported
• prisma/schema.prisma: Language not supported
• src/docs/swagger.json: Language not supported

Comments suppressed due to low confidence (1)

src/controllers/auth.controller.js:897

• The removal of the detailed action (FIREBASE_SIGNUP/FIREBASE_SIGNIN) in the firebaseLogin method decreases logging granularity. If this change is unintentional, reintroducing the descriptive action may help to better trace firebase login activities.

details: {