Ensure new projects have spike thresholds after creation

### Environment

SaaS (https://sentry.io/)

### Steps to Reproduce

1. Create a new project
2. Send a _larger than usual_ amount of events

### Expected Result

Spike Protection should protect new projects (projects that are onboarding) from unexpected Spikes based on what other projects send within the organization.

For context, there have been cases where a new project was onboarded into Sentry and soon after the project was created, it went "rogue" and started sending a lot of events that consumed the org quota for the remaining of the billing cycle. There should be a system within Spike Protection to prevent this.

### Actual Result

Onboarded project was not limited and consumed rest of org's quota for the current billing cycle.

### Product Area

Settings - Spike Protection

### Link

_No response_

### DSN

_No response_

### Version

_No response_

┆Issue is synchronized with this [Jira Improvement](https://getsentry.atlassian.net/browse/FEEDBACK-2003) by [Unito](https://www.unito.io)