feat: persistent memories

[jrasm91]

Dedicated endpoint, service, repository, and database entity for memories, with the goal to make it possible to share, save, and view in the future.

• create a new memory
• update an existing memory (mark is as saved, seenAt)
• delete a memory
• add assets to a memory
• remove assets from a memory

Other thoughts:

• it seems like we need a way to sort them, so there is a memoryAt date field to track the "date" the memory represents. Memories are sorted descending by default so newest memories appear first
• need to add a way to filter memories so "memory lane" is a cross section for the current time period
• need to add a job to auto generate memories based on the current query (and potentially expand this in the future)
• need to update the UI to all the user to "save" or "discard" a memory ( soft? delete)
• need to add a job to automatically delete memories after X days.

[cloudflare-pages]

Deploying immich with    Cloudflare Pages

Latest commit:	9adb005
Status:	✅  Deploy successful!
Preview URL:	https://f7252345.immich.pages.dev
Branch Preview URL:	https://feat-memory-endpoints.immich.pages.dev

View logs

[danieldietzler]

Nice job! :)

[mertalev]

If we want these memories to be shared, do we want this to be handled at a user level?

[jrasm91]

These are only going to be tracked for the owner. I'm not sure what functions shared users will be able to do besides view them in the future. Eventually we could do something like we have planned to do with assets and move owner id off of this table, but it seems premature to try to figure that out now, here.

[mertalev]

Similarly, do we want to store who it's saved by?

[jrasm91]

I'm planning on having this work like Google. So, we'll generate memories and unless the user clicks something to "save" it (set this to true) it will get automatically deleted after 14 days.

[alextran1502]

Do we address #8352 in this PR?

[jrasm91]

Do we address #8352 in this PR?

No. This PR adds the foundation to support persistent memories (adds a new API for them) but it doesn't include automatic memory generation yet. I was planning to do that part in a follow-up pull request.

[alextran1502]

Let's resolve the conflicts and merge it!