Moving most public types to API layer

[jennymar]

Info

Closes #326

Description

What changes did you make? List all distinct problems that this PR addresses. Explain any relevant
motivation or context.

Changes were made to almost all the controller classes in the API layer, as well as their corresponding service classes in the service layer. The mapping of private to public types was moved from the service layer to the API layer.

Changes

API Layer

• AdminController.ts
• AttendanceController.ts
• EventController.ts
• FeedbackController.ts
• LeaderboardController.ts
• MerchStoreController.ts
• UserController.ts

Service Layer

• AttendanceService.ts
• EventService.ts
• FeedbackService.ts
• MerchStoreService.ts
• UserAccountService.ts

Type of Change

• Patch (non-breaking change/bugfix)
• Minor (non-breaking change which adds functionality)
• Major (fix or feature that would cause existing functionality to not work as
  expected)
• Documentation (A change to a README/description)
• Continuous Integration/DevOps Change (Related to deployment steps, continuous integration
  workflows, linting, etc.)
• Other: (Fill In)

If you've selected Patch, Minor, or Major as your change type, make sure to bump the version before merging in package.json!

Testing

I have tested that my changes fully resolve the linked issue ...

• locally.
• on the testing API/testing database.
• with appropriate Postman routes. Screenshots are included below.

Checklist

• I have performed a self-review of my own code.
• I have followed the style guidelines of this project.
• I have appropriately edited the API version in the package.json file.
• My changes produce no new warnings.

Screenshots

Please include a screenshot of your Postman testing passing successfully.

[github-actions]

Thanks for contributing!
If you've made changes to the API's functionality, please make sure to bump the package
version—see this guide to semantic versioning for details—and
document those changes as appropriate.

[maxwn04]

Are we keeping the user profile routes in UserAccountService the same? I think we can still add resumes/social media to the UserModel. Maybe we can change the query as well but that might affect other routes.

membership-portal/services/UserAccountService.ts

Line 195 in 2d73efb

public async getFullUserProfile(user: UserModel) : Promise<PrivateProfile> {