feat(ds): GA Investigation Bias (#8877)

Author: matejminar

src/docs/product/accounts/early-adopter-features/index.mdx

@@ -23,4 +23,3 @@ Limitations:
 - [Priority Sort](/product/issues#issue-sort) algorithm improvements
 - [Issue Reprocessing](/product/issues/reprocessing/)
 - [Span Summary](/product/performance/transaction-summary/#span-summary)
-- [Investigation Mode](/product/performance/retention-priorities/#investigation-mode) for retention priorities in Performance Monitoring

src/docs/product/performance/retention-priorities/index.mdx

@@ -85,8 +85,6 @@ We prioritize low-volume transactions for the same reason we prioritize low-volu
 
 ### Investigation Mode
 
-<Include name="feature-available-for-user-group-early-adopter.mdx" />
-
 Our automated retention priorities work well in a generic manner to collect a baseline of samples because they prioritize retaining data that is valuable for any customer at any given time. However, there are certain scenarios, such as investigating a particular issue, when very specific data becomes temporarily more important. In such cases, sometimes the automated sampling priorities do not provide enough samples, so you may want to create investigation rules.
 
 Investigation rules are sampling rules that can be created through the Sentry UI to temporarily boost the amount of transactions collected for a particular scenario (for example, transactions with specific tag values, etc.). These rules can be created to retain more samples when too few (less than 5) are currently available.