Engineering DRI: @abremard

Describe the bug

When openning the task analysis page and selecting a process, the variables outliers endpoint gets called for every flow node of that process.
This creates a big stress on Elasticsearch and cause crashing.

Expected behaviour

The variables outliers endpoint only get called when viewing the details of a specific flow node.
Hint: This can be done by removing the variables column from the outliers section. The outliers variables are still acessible when the users clicks on "view details" button.

To Reproduce

• Go the Analysis page of optimize
• Go the Task Analysis page
• Open the network tab
• Select a process that has some outliers
• Observe the variableOutliers endpoint getting called for each flow node

Environment observed:

• Optimize mode(s): any
• Optimize version(s): SNAPSHOT, 8.6
• Database(s) (Elasticsearch/OpenSearch): any

Links

related to https://jira.camunda.com/browse/SUPPORT-25625

Breakdown

### Pull Requests
- [ ] https://github.com/camunda/camunda/pull/28107
- [ ] https://github.com/camunda/camunda/pull/28476
- [ ] https://github.com/camunda/camunda/pull/28477

Bug Lifecycle

For managing the issue lifecycle, please use the workflow commands. You can see the available
commands by writing /help as a comment on this issue.

QA Verification

Is this bug reproducible?

• Yes. If so:
  • The bug description is clear
  • The steps to reproduce are clear
  • The environments observed are correct and complete
• No

Review

Engineering Review

• All code targeting the main branch has been reviewed by at least one Engineer
• The PR targeting the main branch has been approved by the reviewing Engineer
• If the API has changed, the API documentation is updated
• All other PRs (docs, controller etc.) in the breakdown have been approved

QA Review

• The change is implemented as described on all target environments/versions/modes
• The documentation changes are as expected

Completion

• All Review stages are successfully completed
• All associated PRs are merged to the main branch(es) and stable branches
• The correct version labels are applied to the issue