Store Latest Crash Dumps

### Problem Statement

One issue we've run into is that our Sentry project has several high volume and long lived issues where the crash dumps we've received are from months ago. These crash dumps generally aren't as relevant as the ones we get from more recent events.

### Solution Brainstorm

It would be nice to be able to configure Sentry to store the x number of most recent crash dumps instead of those first received.

### Product Area

Settings - Security & Privacy

Start with the Settings - Security & Privacy product area and review how crash dumps are currently retained for high-volume, long-lived issues. Define how a configurable number of recent crash dumps should be selected and verify that newer events replace older stored dumps rather than keeping only the first received.

Written by the indexing model from the issue text.