chore(member merge): backfill emails for self-hosted sentry app proxy users

[mifu67]

Dupe of https://github.com/getsentry/getsentry/pull/17808 for self-hosted sentry.

[github-actions]

This PR has a migration; here is the generated SQL for src/sentry/migrations/0997_backfill_self_hosted_sentry_app_emails.py

for 0997_backfill_self_hosted_sentry_app_emails in sentry

--
-- Raw Python operation
--
-- THIS OPERATION CANNOT BE WRITTEN AS SQL

[wedamija]

Any reason we need to make this a job in getsentry at all? We could probably just run this as a post deploy migration and call it a day?

[mifu67]

Any reason we need to make this a job in getsentry at all? We could probably just run this as a post deploy migration and call it a day?

It's been a while and I don't really remember, but I don't see why we couldn't.

[markstory]

Looks good to me. Using migration models for the update will be fine as the outbox handlers for users synchronize data that won't exist in self-hosted, or is not relevant for sentryapp proxy users.

[getsantry]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you remove the label Waiting for: Community, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

[getsantry]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you remove the label Waiting for: Community, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

[getsantry]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you remove the label Waiting for: Community, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀