feat(preprod): Add distribution error endpoint for launchpad

[runningcode]

Add a dedicated endpoint (PUT .../files/preprodartifacts/{id}/distribution/) for launchpad to report distribution processing errors back to the monolith. This mirrors the existing ProjectPreprodSizeEndpoint pattern.

When launchpad encounters a distribution failure (unsupported artifact type, invalid code signature, simulator build), it needs a way to set installable_app_error_code and installable_app_error_message on the artifact so the frontend can display the reason. Previously, the only option was the general update endpoint which marks the entire artifact as failed — but distribution errors shouldn't affect the artifact's overall state.

Follow-up to #109062. The launchpad side that calls this endpoint is in getsentry/launchpad#567.

Refs EME-842, EME-422

[linear]

EME-842 Mirror size analysis NOT_RAN behavior in build distribution

EME-422 Call _update_artifact_error() for unknown artifact types

[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.

[chromy]

is is possible to make this one just an org endpoint? I'm about to delete all the dual registered ones: #109878

[chromy]

lgtm % route

[github-actions]

Backend Test Failures

Failures on 7e8a293 in this run:

tests/sentry/preprod/api/endpoints/test_project_preprod_distribution.py::ProjectPreprodDistributionEndpointTest::test_bad_auth — log

tests/sentry/preprod/api/endpoints/test_project_preprod_distribution.py:34: in test_bad_auth
    assert response.status_code == 401
E   assert 404 == 401
E    +  where 404 = <HttpResponse status_code=404, "text/html; charset=utf-8">.status_code

tests/sentry/preprod/api/endpoints/test_project_preprod_distribution.py::ProjectPreprodDistributionEndpointTest::test_bad_json — log

tests/sentry/preprod/api/endpoints/test_project_preprod_distribution.py:44: in test_bad_json
    assert response.status_code == 400
E   assert 404 == 400
E    +  where 404 = <HttpResponse status_code=404, "text/html; charset=utf-8">.status_code

tests/sentry/preprod/api/endpoints/test_project_preprod_distribution.py::ProjectPreprodDistributionEndpointTest::test_invalid_error_code — log

tests/sentry/preprod/api/endpoints/test_project_preprod_distribution.py:63: in test_invalid_error_code
    assert response.status_code == 400
E   assert 404 == 400
E    +  where 404 = <HttpResponse status_code=404, "text/html; charset=utf-8">.status_code

tests/sentry/preprod/api/endpoints/test_project_preprod_distribution.py::ProjectPreprodDistributionEndpointTest::test_missing_fields — log

tests/sentry/preprod/api/endpoints/test_project_preprod_distribution.py:39: in test_missing_fields
    assert response.status_code == 400
E   assert 404 == 400
E    +  where 404 = <HttpResponse status_code=404, "text/html; charset=utf-8">.status_code

tests/sentry/preprod/api/endpoints/test_project_preprod_distribution.py::ProjectPreprodDistributionEndpointTest::test_non_dict_json_body — log

tests/sentry/preprod/api/endpoints/test_project_preprod_distribution.py:68: in test_non_dict_json_body
    assert response.status_code == 400
E   assert 404 == 400
E    +  where 404 = <HttpResponse status_code=404, "text/html; charset=utf-8">.status_code

tests/sentry/preprod/api/endpoints/test_project_preprod_distribution.py::ProjectPreprodDistributionEndpointTest::test_requires_launchpad_rpc_authentication — log

tests/sentry/preprod/api/endpoints/test_project_preprod_distribution.py:81: in test_requires_launchpad_rpc_authentication
    assert response.status_code == 401
E   assert 404 == 401
E    +  where 404 = <HttpResponse status_code=404, "text/html; charset=utf-8">.status_code

tests/sentry/preprod/api/endpoints/test_project_preprod_distribution.py::ProjectPreprodDistributionEndpointTest::test_set_error — log

tests/sentry/preprod/api/endpoints/test_project_preprod_distribution.py:52: in test_set_error
    assert response.status_code == 200
E   assert 404 == 200
E    +  where 404 = <HttpResponse status_code=404, "text/html; charset=utf-8">.status_code

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

[cursor]

Hardcoded magic number coupled to enum max value

Low Severity

The error_code field uses Field(ge=0, le=3) where 3 is a magic number implicitly coupled to the current max value of InstallableAppErrorCode (PROCESSING_ERROR=3). If a new enum member is added to InstallableAppErrorCode, this Pydantic validation will silently reject the new value with no obvious link back to the enum, making it easy to miss during future updates. Referencing the enum directly (e.g., using its max value or validating membership) would keep the validation in sync automatically.