Sentry Issue: [POSTHOG-821](https://sentry.io/organizations/posthog/issues/3707400683/?referrer=github_integration)

Sentry is reporting that when listing session recordings loading persons is n+1

Looking at how the query works 

we 
* load person distinct ids for recordings in the list
* load the persons that have those distinct ids
* create a fict of distinct id to person
* for each of the recordings
    * look up the  person in the dict and pass them to a `PersonSerializer`
    * that looks up the person's distinct ids while choosing Person's `name`
    * (maybe only when there's no email) in order to determine the first distinct id for the person
    
 That final lookup of distinct ids is (**I think**) where the n plus 1 problem is. 
 
 For each person one at a time we go to the DB and get their distinct ids
 
 There's no foreign key from `Person` to `PersonDistinctId` so we can't utilise `select_related` here. 
 
 _maybe_ we can if we use a list serializer for Persons and then combine the two lists
 
 Some of the reports suggest 50% of the time generating the list is spent loading persons
posthog/api/test/test_session_recordings.py
from datetime import timedelta, timezone
from urllib.parse import urlencode
from dateutil.parser import parse
from dateutil.relativedelta import relativedelta
from django.utils.timezone import now
from freezegun import freeze_time
from rest_framework import status
from posthog.api.session_recording import DEFAULT_RECORDING_CHUNK_LIMIT
from posthog.models import Organization, Person
from posthog.models.session_recording_event import SessionRecordingViewed
from posthog.models.team import Team
from posthog.session_recordings.test.test_factory import create_session_recording_events
from posthog.test.base import APIBaseTest, ClickhouseTestMixin
class TestSessionRecordings(APIBaseTest, ClickhouseTestMixin):
    def setUp(self):
        super().setUp()
        
        self.team = Team.objects.create(organization=self.organization, name="New Team")
    def create_snapshot(