Investigate and fix sync committtee aggregations

[boulder225]

🎯 Problem to be solved

This ticket follows the investigation already happened in https://app.zenhub.com/workspaces/obol-workspace-648c1170ee94656741353327/issues/gh/obolnetwork/charon/3067

Investigate and resolve the issue with the committee aggregation failing when querying endpoints designed for distributed validator clients (DVCs) like Teku. This seems to be the only duty not supported by the latest Teku version.

🛠️ Proposed solution

• Reproduce the issue locally with Teku and document the steps to recreate it.
• Investigate the root cause of the issue, which appears to be a mismatch between the expected and received number of entries in the response from the DVT endpoint.
• Review the Teku codebase and the DVT implementation to understand the expected behavior and any potential changes or optimizations made in the latest version.
• Consult the Teku documentation
• Analyze the logs and error messages from both Teku and the client

[boulder225]

Hey team! Please add your planning poker estimate with Zenhub @gsora @KaloyanTanev @pinebit

[pinebit]

@gsora found this useful article, keeping here for records: https://docs.google.com/document/d/1q9jOTPcYQa-3L8luRvQJ-M0eegtba4Nmon3dpO79TMk/edit#heading=h.mssb0822zapb

[pinebit]

The issue seems gone after we increased number of validators to 512 in kurtosis.
Here is the dashboard: https://grafana.monitoring.gcp.obol.tech/d/b962e704-2e37-48a4-82c0-b15d7661e8a6/charon-overview-v3-testnet-updates?orgId=1&var-cluster_network=testnet&var-cluster_name=test&var-cluster_hash=d0d9162&var-cluster_peer=encouraging-pen&var-job=charon-1&var-peer=All&var-interval=$__auto_interval_interval&var-duty=All&refresh=10s
(rewind to the time of this comment to see the data)

[pinebit]

No issues observed within four hours. Considering the latest Teku as working fine.