[CI] ExponentialHistogramBlockTests testComponentAccess failing

[elasticsearchmachine]

Build Scans:

• elasticsearch-pull-request #105390 / part-3
• elasticsearch-pull-request #105389 / part-3
• elasticsearch-intake #31486 / part3
• elasticsearch-intake #31485 / part3

Reproduction Line:

./gradlew ":x-pack:plugin:esql:compute:test" --tests "org.elasticsearch.compute.data.ExponentialHistogramBlockTests.testComponentAccess" -Dtests.seed=8FFD6A2B2EAF0416 -Dtests.locale=sms -Dtests.timezone=America/Miquelon -Druntime.java=25

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: 
Expected: <1>
     but: was <0>

Issue Reasons:

• [main] 3 consecutive failures in test testComponentAccess
• [main] 2 consecutive failures in step part-3
• [main] 2 consecutive failures in pipeline elasticsearch-pull-request
• [main] 4 failures in test testComponentAccess (2.2% fail rate in 179 executions)
• [main] 2 failures in step part-3 (1.8% fail rate in 109 executions)
• [main] 2 failures in step part3 (5.7% fail rate in 35 executions)
• [main] 2 failures in pipeline elasticsearch-pull-request (1.8% fail rate in 109 executions)
• [main] 2 failures in pipeline elasticsearch-intake (5.7% fail rate in 35 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.

[elasticsearchmachine]

This has been muted on branch main

Mute Reasons:

• [main] 3 consecutive failures in test testComponentAccess
• [main] 2 consecutive failures in step part-3
• [main] 2 consecutive failures in pipeline elasticsearch-pull-request
• [main] 4 failures in test testComponentAccess (2.2% fail rate in 179 executions)
• [main] 2 failures in step part-3 (1.8% fail rate in 109 executions)
• [main] 2 failures in step part3 (5.7% fail rate in 35 executions)
• [main] 2 failures in pipeline elasticsearch-pull-request (1.8% fail rate in 109 executions)
• [main] 2 failures in pipeline elasticsearch-intake (5.7% fail rate in 35 executions)

Build Scans:

• elasticsearch-pull-request #105390 / part-3
• elasticsearch-pull-request #105389 / part-3
• elasticsearch-intake #31486 / part3
• elasticsearch-intake #31485 / part3

[elasticsearchmachine]

Pinging @elastic/es-analytical-engine (Team:Analytics)

[JonasKunz]

I just saw the corresponding mute-PR in the git history. I know the cause, so I'll take care of fixing this. This shouldn't have any production impact as the feature is still behind a feature flag.