Saved Folders Feature

[laurenp-2]

Summary

This pull request implements the folder saving feature, where users can assign apartments to custom folders.

• Implemented api endpoints for the creation, renaming, and deletion of folders
• Implemented api endpoints to add and remove apartments to folders
• Implemented a frontend Folders page where users can see all their folders and the apartments saved to them
• Added a 'Save to folder' popover in apartment pages and cards

Test Plan

Screenshots of the Folders page and Save to Folder modal

Postman was used to test the api endpoints and make sure the backend worked smoothly.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ laurenp-2
❌ Lauren Pothuru

---

Lauren Pothuru seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[dti-github-bot]

[diff-counting] Significant lines: 1911. This diff might be too big! Developer leads are invited to review the code.

[parsa-tehranipoor]

Super cool feature Lauren! Your backend routes look really polished and nicely organized. You followed our coding conventions really well, which made understanding your work 10x easier. The UI from the screenshots above also looks really nice. Nice job!

[CasperL1218]

Great work. Code structure is organized, well-documented, and the inline component comments are helpful (e.g. AddToFolderPopover.tsx)
Some future points of consideration for feature expansions:

• Shared folder ownership: The current document structure for folders uses a single user value, which will need to change to support co-ownership.
• Proposed solution: Replace the string-based user field with an array to accommodate multiple users.

Implementation requirements:

• change to user-id based query logic (@route GET /api/folders)
• persistence logic for multiple owners (e.g. modified deletion in @route DELETE /api/folders/:folderId to remove specific users rather than deleting the entire folder).

These will be future requirements. Current implementation is great. Well done.