Fix wrong sync committee participation association

[manuelsc]

Note that this PR restores functionality of the sync committee stats and does not aim to fully support the edge case of a validator being part of the same sync committee twice as this requires a wider refactor of how we handle sync committees on the frontend. Will create a jira task for that special case.

Main culprit of current approach was that the de duplication on statistics exporter level shuffled the sync committee index. Removed de duplication in this level since a validator can be elected into the same sync committee multiple times and kept current frontend handling (which does not handle this case at all atm, but so far this hasn't occurred on mainnet or prater yet.)

Requires a re-export via misc tool, command:

misc \
--command=export-sync-committee-periods \
--dry-run=false \
--config path_to_config.yml \
&& misc \
--command=export-sync-committee-validator-stats \
--dry-run=false \
--config path_to_config.yml \
&& misc \
--command=export-stats-totals \
--columns=missed_attestations_total,participated_sync_total,missed_sync_total,orphaned_sync_total \
--day-start=0 \
--day-end=0 \
--dry-run=false \
--config path_to_config.yml

Fun Fact: Sync period 827 is utterly wrong on prater db, every one of the 512 validators has a second entry with a different committee indices. Should be fixed via re-export also.

🤖 Generated by Copilot at b3baa4a

This pull request fixes various bugs and inconsistencies in the sync committee data for validators, both in the exporter and the API handler. It also improves the SQL queries and adds comments to make the code more clear and reliable.

[LuccaBitfly]

Sorry, wasn't aware that the sync reexport tools are gone so I didn't look at exportSyncCommitteeValidatorStats in my first review.

[LuccaBitfly]

lgtm