refactor: move asset stacks to their own entity

[zackpollard]

Refactor to move asset stacks to their own entity. This is the first part of this work. Bundled into this is also some initial work for auto-stacking burst assets.

To Do:

• Add SQL migrations for existing stacks to move to new table format

Further Work (Different PR(s)):

• Add FK constraint so primaryAssetId must exist within the same stack
• Check test cases and add more for asset stacking
• Finish burst auto-stacking work
• Refactor stacking to have a asset-stack service and repository, rework API calls from mobile and web to use new APIs for stack operations
• Migrate live photos to use these stacks (Add stack type to stack entity)

[cloudflare-pages]

Deploying with    Cloudflare Pages

Latest commit:	19dc1d8
Status:	✅  Deploy successful!
Preview URL:	https://8b815637.immich.pages.dev
Branch Preview URL:	https://feat-auto-stack-burst-photos.immich.pages.dev

View logs

[jrasm91]

Looks pretty good, although I am having a hard time wrapping my head about the actual stacking/unstacking logic.

[jrasm91]

It looks like an entire asset-stack CRUD api exists inside of the bulk asset update endpoint now 😆, besides that I think this looks great. I was able to test creating stacks with the new code, as well as migrating from main to this branch and back again, all without losing existing stacks.