chore: add migration to replace indexes with new unique ons

[wwrk22]

What's the change?

Migration to replace StandupMeetingGroupUser indexes with new unique ones.

What key workflows are impacted?

N/A

Highlights / Surprises / Risks / Cleanup

N/A

Demo / Screenshots

N/A

Issue ticket number and link

#251

Checklist before requesting a review

• Did you consider risks around security, performance, etc.?
• Related to readability and consistency: Did you add comments and/or documentation? (README, Notion, etc.)
• Did you leave helpful inline PR comments for the reviewer(s)?
• Did you include instructions for how to test in the ticket?
• Did you add any relevant tags and decide if this PR is a Draft vs. Ready for Review?
• Do you have a plan for how this change should be rolled back? (e.g., how do you deal with a migration rollback? Is your feature released behind a feature flag?)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (b0568c7) 98.93% compared to head (9d2386e) 98.94%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #435   +/-   ##
=======================================
  Coverage   98.93%   98.94%           
=======================================
  Files         214      215    +1     
  Lines        3207     3221   +14     
=======================================
+ Hits         3173     3187   +14     
  Misses         34       34           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[toyhammered]

This looks good. You generally point this towards your other branch that is required to go first so this doesn't accidentally get merged in before.

[wwrk22]

This looks good. You generally point this towards your other branch that is required to go first so this doesn't accidentally get merged in before.

Aha, that makes sense.

[wwrk22]

@toyhammered
Made a couple of commits to update the model spec.