feat(hogql): Use distinct_id-based person overrides for PERSON_ID_OVERRIDE_PROPERTIES_JOINED mode

[tkaemming]

Problem

#21504 did not implement reading from the new person_distinct_id_overrides table as the source for overrides, but that is the table we eventually want to use for HogQL queries as it has all of the data necessary to be transparently substitutable with the equivalent queries that do joins on the full person_distinct_id2 table.

Changes

This updates the PERSON_ID_OVERRIDE_PROPERTIES_JOINED mode to use the new person_distinct_id_overrides table. This change should be safe to make for this version, since nobody was previously opted into this mode. The data returned by this mode should be generally the same as the data returned when not opted into any particular mode, so it should be safe to move teams in and out of this mode without any noticeable impact beyond improved performance.

This leaves PERSON_ID_OVERRIDE_PROPERTIES_ON_EVENTS using the old table, and we can determine the upgrade path for those teams independently.

This will result in support for legacy and HogQL queries for the modes introduced in #21504 as shown:

Mode	Overrides	Legacy	HogQL
DISABLED	N/A	Yes	Yes
PERSON_ID_NO_OVERRIDE_PROPERTIES_ON_EVENTS	N/A	Yes	Yes
PERSON_ID_OVERRIDE_PROPERTIES_ON_EVENTS	person_overrides (v2)	Yes	Yes
PERSON_ID_OVERRIDE_PROPERTIES_JOINED	person_distinct_id_overrides (v3)	No	Yes

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

Yes, this nobody should be using the override query modes.

How did you test this code?

Updated tests, also manually verified some queries via /debug.

[github-actions]

Size Change: +155 kB (+18%) ⚠️

Total Size: 999 kB

Filename	Size	Change
frontend/dist/toolbar.js	999 kB	+155 kB (+18%)	⚠️

_{compressed-size-action}