perf: Enable property group optimizations for all new teams by default

[tkaemming]

Problem

New teams still use the slower path even though they don't have any data that needs backfilling.

Changes

This changes the default value of modifiers so that all teams use the new path (see: #24152, #24171, #24381, #24897 for details.)

This could also be done with a feature flag but this has a couple advantages:

• we're already using modifiers in production for this, so change is minimal and avoids adding new layers of configuration (like what happened with the PoE rollout)
• allows hobby deployments to use the new functionality for new projects without any extra work beyond the typical "run migrations" step

It does have some disadvantages though, too:

• can't do double duty as a kill switch in an emergency
• it is less auditable who made changes and when
• includes a migration with a clumsy import back into application code

I couldn't really make up my mind on which approach was "best" so just defaulted to the least impact change since the likelihood that we'll need a kill switch seems minimal (we've been testing this for a while — and worst case we can just run an UPDATE to drop the modifier for all teams if we have to) and most if not all teams should be able to be migrated to this in the coming days. (After this is merged, I'm planning on updating all teams that were created after we started writing events with property groups to use this optimization, in fact.)

Does this work well for both Cloud and self-hosted?

Yes: see above, this turns it on for new projects in self-hosted as well.

How did you test this code?

See updated snapshots.