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.

### Solution Brainstorm

Use different baselining window depending on project platform.

### Product Area

Settings - Spike Protection