Support incrementally updating group properties

[macobo]

Is your feature request related to a problem?

Currently, group properties can only be updated all at once.

Additionally, the created_at column on groups is a lie (it's actually last_updated)

Describe the solution you'd like

Use the same new pattern team platform has settled on for updating person properties. Likely this will include some form of:

• Storing the group properties in postgres as well
• Doing versioning.

Exact details TBD.

Describe alternatives you've considered

Not supporting incremental updates. This works for now, but see below for a reason to do it.

Additional context

This has become blocker for #7010 as well as querying clickhouse in /decide endpoint is not really ideal.

Thank you for your feature request – we love each and every one!

[yakkomajuri]

Dump from Slack:

#6834 is the place with the most context.
But the TL;DR is:
Me and Tiina laid out how a property should be updated based on the following variables: the event timestamp, the last timestamp of a property update, the current operation (set/set_once), and the previous operation (set/set_once).
Based on the above, you should lock a groups row (with SELECT FOR UPDATE), calculate the property updates, and issue the update.
A lot of the logic for checking is already in place.

You’d need a Postgres table with at least properties, properties_last_updated_at , and properties_last_operation.

[yakkomajuri]

I also would recommend the follow-up to this being the equivalent version work #6667

[macobo]

Chatted with @yakkomajuri how to go about this. Notes from that:

• We'll go forward with this - person updates in particular are now in and ready to be followed as a pattern.
• Important columns for the postgres table are properties, properties_last_operation, properties_last_updated_at all jsonb and version, which is populated for pg.
• During updates we should lock relevant rows (SELECT FOR UPDATE)
• For clickhouse version is not yet ready and I won't be building for it now. Doing this depends on either EPIC: Handling big migrations for self-hosted users #7054 or doing it in a slightly smarter way. Will follow up with this with #team-platform later

[macobo]

Initial support for this has landed!