Wider baseline window for Spike Protection threshold for Mobile/Desktop

### Problem Statement Because mobile/desktop release cycles take days or weeks, Spike Protections 1-week baseline algorithm is ineffective at catching even most extreme spikes in new releases as they ramp up gradually with slow adoption of the new release by end-users. Below is an example from 1 "monster" issue in an Android projects that devoured 13M errors over a week leading to large overage bill at the end of the month for a mid-to-large size Enterprise customer. <img width="1061" alt="Screenshot 2024-04-08 at 2 21 50 PM" src="https://github.com/getsentry/sentry/assets/490201/ec20e4f1-4a54-4ea8-9e49-4c7b7422c70d"> <img width="1064" alt="monster-13M" src="https://github.com/getsentry/sentry/assets/490201/0744eec7-3428-40d7-8c07-54483ad068b8"> ### Solution Brainstorm Use different baselining window depending on project platform. ### Product Area Settings - Spike Protection