Add names to retroactive attendance form

[ryanDing26]

Info

Closes #322.

Description

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

Faris wanted to change the functionality on the retroactive attendance form (within the admin dashboard) so that it displayed names in the format firstName lastName (email) so that it would be easier to autocomplete manual attendance by name instead of asking people for their email for points.

Changes

• Changed the emailRaw variable in getAllEmails in UserRepository.ts such that it built a query with the firstName and lastName of a user from the UserModel object alongside the existing email selection
• Changed the return statement of getAllEmails in UserRepository.ts such that instead of just mapping all the emails, it would map firstName lastName (email)

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.

[nik-dange]

Just a small nit. You'll need to fix your tests and run the linter before being able to merge though, make sure those pass before opening a PR

[dowhep]

Nit: Since you will be returning an array of strings that concatenate names and emails, it would be cleaner and more correct to define a new type for such strings. Maybe make the field name "namesAndEmails" or something.

[nik-dange]

lgtm. please bump package version before merging

[farisashai]

sorry I have one quick but important nit

[ryanDing26]

This is the final version I would like to submit for the PR. Let me know if any more changes need to be made!

[nik-dange]

One quick question

[echang594]

See my other comment

[nik-dange]

@ryanDing26 looks good to me, just threw in a return type and did some linting

lgtm