Revert "Do not send member updates to all (#3431)"

[pcapriotti]

Looks like preventing team events from being sent to regular team users has some consequences for clients, not just the team settings app.

This PR reverts the changes to the team event propagation logic, but keeps the schema and data migrations (used for indexing team admins) in place.

Checklist

• Read and follow the PR guidelines

[jschaul]

Since the galley data migration has now already run; I think we should keep the logic which writes and deletes to the new table in place. And only revert the business logic about who gets events. Otherwise we get a gap of events not recorded in that table from t0=this-PR-deployed to t1=future-time-where-new-PR-gets-deployed.

[pcapriotti]

Since the galley data migration has now already run; I think we should keep the logic which writes and deletes to the new table in place. And only revert the business logic about who gets events. Otherwise we get a gap of events not recorded in that table from t0=this-PR-deployed to t1=future-time-where-new-PR-gets-deployed.

Good point, I didn't think of that. Should be fixed by the latest commit. It's a bit unfortunate that now we have to fetch admins just to check the admin limit, and not use them for notifications. An alternative would be to leave things as they used to be, and re-run the data migration next time. But I guess this is fine.