Cleaning up the options documentation to prevent future confusion (#14419)

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

## DESCRIBE YOUR PR
*Tell us what you're changing and why. If your PR **resolves an issue**,
please link it so it closes automatically.*

## 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 -->
- [ x ] 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/)

Author: kneeyo1

develop-docs/backend/application-domains/options.mdx

@@ -5,9 +5,15 @@ sidebar_order: 10
 
 Options are a way to store generic system-wide configuration. They serve a similar purpose to configuration files, but they are backed by a database, so it's possible to change them at runtime without a deploy. Options are stored in the database and cached, so they are performant and reliable. This makes options well-suited for rates, quotas, and limits.
 
+While the process for creating and using options in the codebase is universal, the method for *managing their values* differs between Sentry's internal SaaS platform and self-hosted instances.
+
+> **For Sentry Employees**
+>
+> Option management for Sentry's internal SaaS environments is handled via a GitOps workflow. All changes to option values are proposed, reviewed, and deployed through pull requests. For complete details on changing values, handling drift, and deployment, please see the **[sentry-options-automator](https://github.com/getsentry/sentry-options-automator)** repository.
+
 ## Adding New Options
 
-To add a new system option, add it to [`sentry/options/defaults.py`](https://github.com/getsentry/sentry/blob/master/src/sentry/options/defaults.py) by registering it. e.g.,
+The process for registering a new option is the same for all environments and is done in the Sentry codebase. Add your option to [`sentry/options/defaults.py`](https://github.com/getsentry/sentry/blob/master/sentry/options/defaults.py).
 
 ```python
 register("performance.some-feature-rate", default=0.0)
@@ -23,24 +29,23 @@ Follow these rules when adding new options:
 The value of an option can be any pickleable value.
 
 <Alert>
-  It is safe to declare and use an option in the same pull request, you don't need to
-  split them up.
+  It is safe to declare and use an option in the same pull request; you don't need to split them up.
 </Alert>
 
 ## Using Options
+To check the value of an option, import the options module and use the get method. This is universal across all environments.
 
-To check the value of an option, import the `options` module and use the `get` method. e.g.,
 
 ```python
 from sentry import options
 feature_rate = options.get("performance.some-feature-rate")
 ```
 
 ## Setting Options
-
-You can change the value of an option using `sentry shell`, or by using the [options UI](#options-ui).
+For self-hosted instances, you can change the value of an option using `sentry shell`, or by using the [options UI](#options-ui).
 
 ### Sentry Shell
+For direct database manipulation, you can set option values using sentry shell.
 
 You can set option values using `sentry shell`. e.g.,
 
@@ -110,7 +115,9 @@ def test_some_feature(self):
 
 ## Removing Options
 
-If your option is short-lived, you should remove it once it's no longer needed. First, create a pull request to remove the option and its usage. Once it's merged and deployed, remove the option from the database. To do this, you can use the Sentry shell. e.g.,
+If your option is short-lived, you should remove it once it's no longer needed. First, create a pull request to remove the option and its usage. Once it's merged and deployed, remove the option from the database. For self-hosted instances, this is done via the Sentry shell. Otherwise, remove it from the Options Automator repository.
+
+For self hosted instances, you can use the Sentry shell. e.g.,
 
 ```bash
 sentry shell
@@ -122,8 +129,3 @@ then,
 from sentry import options
 options.delete("performance.some-feature-rate")
 ```
-
-<Alert>
-  If you do not have access to the shell, you'll need to contact OPS to remove the option
-  for you.
-</Alert>