fix(personhog_client): person team mismatch metric overcounting

[nickbest-ph]

Problem

The person team mismatch metric being emitted by personhog client lookups was overcounting. It inadvertently counted any distinct id that no longer has a matching person as a person team mismatch.

Changes

• first filter returned persons lists by team mismatch, store the list then filter that list on whether the person record exists/has an id
• use the two arrays to calculate the true number of persons filtered due to a team mismatch

How did you test this code?

• there are plenty of unit/integration tests making sure this didn't change any behaviour

[greptile-apps]

Important Files Changed

Filename	Overview
posthog/models/person/util.py	Three metric-counting sites updated to separate 'person not found' cases from true team-mismatch cases. Correct and consistent across all three locations.
posthog/queries/actor_base_query.py	One additional metric-counting site updated with the same fix, keeping _fetch_people_via_personhog consistent with the util.py changes.

_{Reviews (1): Last reviewed commit: "fix(personhog_client): person team misma..." | Re-trigger Greptile}

[github-actions]

🎭 Playwright report · View test results →

⚠️ 2 flaky tests:

• Redirect to appropriate place after login with complex URL (chromium)
• Deleting a dashboard navigates to the dashboards list (chromium)

These issues are not necessarily caused by your changes.
Annoyed by this comment? Help fix flakies and failures and it'll disappear!