Support for 'developer mode' or 'non-retail mode'

### Problem Statement

Ability to support a title that's only in developer scenarios and not yet in release, that has different constraints outside retail. This way it can support very specific use cases and not impact retail such as lower error volume, higher fidelity, larger artifacts, flight rings, etc.

### Solution Brainstorm

_No response_

### Product Area

Unknown

No files, tests, or entry points are named. Start by clarifying the product area and the constraints that distinguish developer or non-retail mode from retail, then identify the affected Sentry components and define acceptance criteria for supporting those differences without changing retail behavior.

Written by the indexing model from the issue text.