feat(sentry): update feature flags and enhance organization

[TartanLeGrand]

🎯 Objective

Reorganize and optimize Sentry feature configuration in the Helm chart template for better maintainability and conditional feature management.

📋 Changes Made

1. Feature Configuration Restructuring

• Conditional Feature Management: Implemented dynamic feature activation based on values.yaml configuration
• Eliminated Duplicates: Removed duplicate feature declarations between conditional and always-enabled feature lists
• Values-Based Control: Added support for granular feature control through sentry.features in values.yaml

2. Supported Feature Toggles

The following features can now be controlled via values.yaml:

• orgSubdomains: Organization subdomain ingestion (false by default)
• enableProfiling: Application profiling features (false by default)
• enableSessionReplay: Session replay functionality (true by default)
• enableFeedback: User feedback features (false by default)
• enableSpan: Span tracking and metrics (false by default)
• vstsLimitedScopes: VSTS integration scopes (true by default)

3. Feature Organization by Category

• Reorganized always-enabled features into logical categories:
• Core Features: Authentication, authorization, basic functionality
• Alerting & Monitoring: Alert management, anomaly detection
• Performance Monitoring: Transaction tracking, metrics, APM
• AI & Machine Learning: Seer integration, GenAI features
• Integrations: GitHub, Jira, external service connections
• UI & Dashboard: Interface improvements, navigation
• Workflow Engine: Automation and workflow management
• Specialized Features: Our Logs, mobile tracking, etc.

4. Code Quality Improvements

• Enhanced Readability: Clear categorization with descriptive comments
• Maintainability: Easier to locate and modify specific feature groups
• No Breaking Changes: Maintains backward compatibility with existing configurations

[TartanLeGrand]

Plus I have enabled temporary features by default and we get the new ui 🎊

[Mokto]

Let me know when it passes tests

[cjcormack]

I am happy to try and help get this mergeable. The thing that I am currently trying to understand is from where the current list of feature flags is coming? Looking in the self-hosted repo, I think that the list wants to be based on:

• All of the features in: https://github.com/getsentry/self-hosted/blob/25.7.0/sentry/sentry.conf.example.py#L283
• The feature flags listed in the issues in https://github.com/getsentry/self-hosted/labels/Type%3A%20Pre-release%20Feature (which have instructions <= 25.7.0 and we have support in the charts).

Going forward, this is probably something that we want to keep synchronised when updating to a new Sentry build.

[TartanLeGrand]

The list of features are in :

• https://github.com/getsentry/sentry/blob/9ed4ed8c78e6163eb443023a05ef37b3739cb82a/src/sentry/features/permanent.py
• https://github.com/getsentry/sentry/blob/9ed4ed8c78e6163eb443023a05ef37b3739cb82a/src/sentry/features/temporary.py

[TartanLeGrand]

@cjcormack can you review this ? 😄

[Mokto]

👋 Hi, @TartanLeGrand,
I detected conflicts against the base branch 🙊
You'll want to sync 🔄 your branch with upstream!

[patsevanton]

Could you rebase PR ?