doc(perf-scale): Remove starred transactions

src/docs/product/performance/performance-at-scale/index.mdx

@@ -33,7 +33,6 @@ Retention priorities are enabled by default, but can be disabled individually in
 |-------------------------|---------------|
 | Latest Release          | Health Checks |
 | Dev Environments        |               |
-| Starred Transactions    |               |
 | Low Volume Projects *   |               |
 | Low Volume Transactions |               |
 
@@ -50,12 +49,6 @@ While prioritizing data from the latest release, we also take into consideration
 
 We prioritize data from development environments because these environments typically generate a relatively small number of transactions compared to your production environments. As a result, to gain meaningful insights during your testing phase, we prioritize transaction data from these environments.
 
-### Starred Transactions
-
-Typically, for most projects there are only a few transactions that you really care about. We prioritize [starred transactions](/product/performance/transaction-summary/#starring-key-transactions) over others, so you can have more visibility into your important data.
-
-![Starred Transactions](starred_transactions.png)
-
 ### Health Checks
 
 _Health check_ type transactions, while important for checking the stability of your application, don't have any value for you beyond the task associated with them. For this reason, we keep fewer samples of these types of transactions and instead prioritize retaining more samples of your other more valuable transactions.