fix(ai-insights): remove sampling mode from query

[obostjancic]

Fixes: SENTRY-5BD5

• Removes sampling mode from the conversation query
• Adds extra logging
• Temporarily narrows down date time params

[seer-by-sentry]

Bug: First query uses sampling_mode=None instead of HIGHEST_ACCURACY for AI conversation ID discovery.
_{Severity: CRITICAL | Confidence: 1.00}

🔍 Detailed Analysis

The initial query for discovering AI conversation IDs uses sampling_mode=None. This violates explicit repository requirements stating that AI conversation data queries must use sampling_mode="HIGHEST_ACCURACY" to ensure complete and non-extrapolated results. This leads to silently returning incomplete conversation data.

💡 Suggested Fix

Change sampling_mode=None to sampling_mode="HIGHEST_ACCURACY" for the initial conversation ID discovery query to comply with data completeness requirements.

🤖 Prompt for AI Agent

Fix this bug. In src/sentry/api/endpoints/organization_ai_conversations.py at lines
126-130: The initial query for discovering AI conversation IDs uses
`sampling_mode=None`. This violates explicit repository requirements stating that AI
conversation data queries must use `sampling_mode="HIGHEST_ACCURACY"` to ensure complete
and non-extrapolated results. This leads to silently returning incomplete conversation
data.

_{Did we get this right? 👍 / 👎 to inform future reviews.}

[obostjancic]

The initial query for discovering AI conversation IDs uses sampling_mode=None. This violates explicit repository requirements stating that AI conversation data queries must use sampling_mode="HIGHEST_ACCURACY" to ensure complete and non-extrapolated results. This leads to silently returning incomplete conversation data.

While it is true that with sampling_mode=None some results might be sampled out, the "repository requirements" seem to be completely hallucinated

[codecov]

❌ 1 Tests Failed:

Tests completed	Failed	Passed	Skipped
41361	1	41360	250

View the top 1 failed test(s) by shortest run time

tests.sentry.api.endpoints.test_organization_ai_conversations.OrganizationAIConversationsEndpointTest::test_complete_conversation_data_across_time_range

Stack Traces | 4.78s run time

#x1B[1m#x1B[.../api/endpoints/test_organization_ai_conversations.py#x1B[0m:473: in test_complete_conversation_data_across_time_range
    assert conversation["llmCalls"] == 2
#x1B[1m#x1B[31mE   assert 1 == 2#x1B[0m

To view more test analytics, go to the Test Analytics Dashboard
_{📋 Got 3 mins? Take this short survey to help us improve Test Analytics.}

[vgrozdanic]

this should be imported from python std lib, right?

[cursor]

Bug: Logging Fails with Non-Serializable Data

The json.dumps calls in logging statements (lines 181, 255, 262) operate on raw Snuba query results. These results can include non-JSON-serializable types like Decimal, which causes a TypeError and crashes the API endpoint.