Add new billing docs for Seer (#13977)

<!-- Use this checklist to make sure your PR is ready for merge. You may
delete any sections you don't need. -->

## DESCRIBE YOUR PR
See preview on:
https://sentry-docs-git-seer-billing.sentry.dev/pricing/quotas/manage-seer-budget/

## IS YOUR CHANGE URGENT?  

Help us prioritize incoming PRs by letting us know when the change needs
to go live.
- [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE -->
- [ ] Other deadline: <!-- ENTER DATE HERE -->
- [ ] None: Not urgent, can wait up to 1 week+

## SLA

- Teamwork makes the dream work, so please add a reviewer to your PRs.
- Please give the docs team up to 1 week to review your PR unless you've
added an urgent due date to it.
Thanks in advance for your help!

## PRE-MERGE CHECKLIST

*Make sure you've checked the following before merging your changes:*

- [ ] Checked Vercel preview for correctness, including links
- [ ] PR was reviewed and approved by any necessary SMEs (subject matter
experts)
- [ ] PR was reviewed and approved by a member of the [Sentry docs
team](https://github.com/orgs/getsentry/teams/docs)

## LEGAL BOILERPLATE

<!-- Sentry employees and contractors can delete or ignore this section.
-->

Look, I get it. The entity doing business as "Sentry" was incorporated
in the State of Delaware in 2015 as Functional Software, Inc. and is
gonna need some rights from me in order to utilize my contributions in
this here PR. So here's the deal: I retain all rights, title and
interest in and to my contributions, and by keeping this boilerplate
intact I confirm that Sentry can use, modify, copy, and redistribute my
contributions, under Sentry's choice of terms.

## EXTRA RESOURCES

- [Sentry Docs contributor guide](https://docs.sentry.io/contributing/)

---------

Co-authored-by: Alex Krawiec <[email protected]>
Co-authored-by: Isabella Enriquez <[email protected]>

Author: 3 people

.vscode/settings.json

@@ -14,6 +14,7 @@
     "**/src/wizard/**": true
   },
   "cSpell.words": [
+    "fixability",
     "laravel",
     "subprocessor",
     "subprocessors"

docs/pricing/quotas/img/manage-seer-budget-01.png

@@ -0,0 +1,53 @@
+---
+title: Manage Your Seer Budget
+sidebar_order: 40
+description: "Understand where and how to manage your Seer budget, see which projects are consuming more than others, and how to increase or decrease your spend."
+---
+
+<Alert>
+[Seer](/product/ai-in-sentry/seer/) is only available when purchased additionally while on a Team or Business plan. Once Seer has been purchased, your subscription will have $25 worth of Seer budget to be used across issue scans and issue fixes.
+</Alert>
+
+## Key Terms
+
+- **Seer Budget**: The initial budget your subscription has allocated to be used exclusively by Seer products. This includes issue scans and issue fixes.
+
+- **Pay-As-You-Go (PAYG) Budget**: A budget you set to pay for additional issue scans and fixes beyond your Seer budget.
+
+- **Issue Scan**: An analysis of an issue to help determine fixability. These scans are run automatically for every new error and performance issue.
+
+- [**Issue Fix**](/product/ai-in-sentry/seer/issue-fix/): A root cause and solution generated for an issue. You will only be charged one fix per issue, however if you "Start Over" your fix, this will count as a new fix and will be charged accordingly.
+
+## Before You Begin: Check Your Seer Usage
+
+You can look at your Seer usage in the [Usage Stats tab](/product/stats/#usage-stats) to understand the breakdown of your issue fixes and issue scans by time window and project. This may help you figure out where you need to further fine-tune your usage.
+
+This page is accessible to all members of your organization, so Owners in your Sentry org will be able to share it with the developers directly responsible for a given project. You'll also be able to use this page to assess whether your changes are working as intended.
+
+### How Can I See a Breakdown of Incoming Issue Scans and Fixes?
+
+The Usage Stats tab displays details about the total amount of data Sentry has received across your entire org for up to 90 days. The page breaks down the events by project into three categories: accepted, dropped, or filtered. Only accepted scans and fixes affect your budget: 
+
+![Stats and Usage page example](./img/manage-seer-budget-01.png)
+
+### Which Projects Are Consuming My Seer Spend?
+
+The "All Projects" table on the Stats page breaks down your data by project, so you can identify the ones that are consuming the most budget. Clicking on the settings icon next to a project name in the table will open that project's settings page, where you can manage its Seer scan and automatic analysis settings.
+
+## Adjusting PAYG Budget
+
+Budgets can only be updated by a Billing- or Owner-level member of your Sentry org.
+
+Once your Seer budget is approaching or has exceeded its included budget, teammates with "Owner" org permissions will start receiving [notification](/product/alerts/notifications/#quota-notifications) emails. They'll then be able to choose to increase or decrease the PAYG budget to unlock additional usage.
+
+
+### Increasing Seer Budget
+If Issue Scans have stopped running or you're not able to initiate new Issue Fixes because you've exceeded your Seer budget, you can add to your budget at any time during your billing period by increasing your PAYG budget. This is ideal in situations where you're rolling out a new version of your application, for example. To add PAYG budget, set a monthly maximum shared budget in your [Subscriptions Page](https://sentry.io/orgredirect/organizations/:orgslug/settings/billing). 
+
+[Learn more about setting your PAYG budget](/pricing/#pricing-how-it-works).
+
+## Managing Spend
+
+### Seer Fix and Scan Automation Settings
+
+If you find that you're running out of your Seer or PAYG budget too quickly, you can double-check your project's Seer automation settings. To ensure new projects are in check, you can also update the default settings for new projects. For more details on choosing the right automation settings for you, visit the Automation Settings docs.