Crash-free session and user metrics should break down by environment and release rather than requiring project separation

Problem Statement Teams that want crash-free rate segmented by build type, platform, or deployment stage end up creating a separate Sentry project per segment, because that is the level at which the metric is reliably reported and compared. This pushes a data-model concern into the project structure, and it has real costs. Symbols, alert rules, ownership rules, integrations, and grouping configuration all have to be duplicated per project and kept in sync, and they drift. Cross-segment comparison gets harder rather than easier, because the segments now live in different projects. Environment and release already exist as the intended dimensions for exactly this kind of segmentation. Teams that have correctly modelled their builds as environments and releases are currently penalised relative to teams that split by project, which is the wrong incentive. Release health comparison across environments, internal build versus public build or one platform versus another, is the primary que…