feat(preprod): add endpoint to fetch dashboard data

[trevor-e]

Adds a new endpoint we can query from Dashboards to fetch preprod EAP data.

[github-actions]

🚨 Warning: This pull request contains Frontend and Backend changes!

It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently.

Have questions? Please ask in the #discuss-dev-infra channel.

[codecov]

Codecov Report

❌ Patch coverage is 61.62162% with 71 lines in your changes missing coverage. Please review.
✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
...i/endpoints/organization_preprod_app_size_stats.py	60.55%	71 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           master   #105309      +/-   ##
===========================================
- Coverage   80.56%    80.54%   -0.02%     
===========================================
  Files        9443      9444       +1     
  Lines      404657    404926     +269     
  Branches    25722     25722              
===========================================
+ Hits       326002    326160     +158     
- Misses      78223     78334     +111     
  Partials      432       432              

[sentry]

Bug: The optional filter query, triggered by includeFilters=true, lacks error handling. A failure in the underlying Snuba RPC call will crash the entire endpoint.
_{Severity: HIGH | Confidence: High}

🔍 Detailed Analysis

The endpoint handles errors for the main data query but not for the optional filter data query triggered when includeFilters=true. The _fetch_filter_values method calls query_preprod_size_metrics without a try-except block. Since query_preprod_size_metrics can raise several exceptions (e.g., SnubaRPCError), a failure in this optional part of the request will cause the entire endpoint to return a 500 error, even if the main data was successfully retrieved. This violates the principle that optional enhancements should not crash core functionality.

💡 Suggested Fix

Wrap the call to self._fetch_filter_values within a try-except block. In the except block, log the error and gracefully degrade by returning the main data without the filter values, or by setting filter_values to an empty dictionary. This ensures that a failure in the optional filter query does not impact the primary functionality of the endpoint.

🤖 Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location:
src/sentry/preprod/api/endpoints/organization_preprod_app_size_stats.py#L117-L120

Potential issue: The endpoint handles errors for the main data query but not for the
optional filter data query triggered when `includeFilters=true`. The
`_fetch_filter_values` method calls `query_preprod_size_metrics` without a `try-except`
block. Since `query_preprod_size_metrics` can raise several exceptions (e.g.,
`SnubaRPCError`), a failure in this optional part of the request will cause the entire
endpoint to return a 500 error, even if the main data was successfully retrieved. This
violates the principle that optional enhancements should not crash core functionality.

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