feat: add sync committee pool & GET /eth/v1/validator/sync_committee_contribution endpoint

[ShiroObiJohn]

What was wrong?

Fixes #238

How was it fixed?

implemented GET /eth/v1/validator/sync_committee_contribution endpoint.
added sync committee pool to manage sync committee messages and contributions.

To-Do

• I have read CONTRIBUTING.md.
• This PR title follows conventional commits.

[shariqnaiyer]

Could you please rebase this? I shall review it once you have.

git fetch upstream
git rebase upstream/master

[ShiroObiJohn]

Could you please rebase this? I shall review it once you have.

git fetch upstream
git rebase upstream/master

@shariqnaiyer rebased. Thank you!

[shariqnaiyer]

Overall looks good, I wonder why sync committee pool is optional and is made none in most store initializations? Is that intentional?

[ShiroObiJohn]

Overall looks good, I wonder why sync committee pool is optional and is made none in most store initializations? Is that intentional?

Yes. Only some of sync committee related Beacon API endpoints need to access it.

[shariqnaiyer]

https://github.com/ReamLabs/ream/blob/master/crates/networking/manager/src/gossipsub/handle.rs#L267-L295

            GossipsubMessage::SyncCommittee((sync_committee, subnet_id)) => {
                info!(
                    "Sync Committee received over gossipsub: root: {}",
                    sync_committee.tree_hash_root()
                );

                match validate_sync_committee(&sync_committee, beacon_chain, subnet_id, cached_db)
                    .await
                {
                    Ok(validation_result) => match validation_result {
                        ValidationResult::Accept => {
                            p2p_sender.send_gossip(GossipMessage {
                                topic: GossipTopic::from_topic_hash(&message.topic)
                                    .expect("invalid topic hash"),
                                data: sync_committee.as_ssz_bytes(),
                            });
                        }
                        ValidationResult::Reject(reason) => {
                            info!("Sync committee message rejected: {reason}");
                        }
                        ValidationResult::Ignore(reason) => {
                            info!("Sync committee message ignored: {reason}");
                        }
                    },
                    Err(err) => {
                        error!("Could not validate sync committee message: {err}");
                    }
                }
            }

We want to populate the sync committee pool. I believe we will have to add them once we see it in gossip messages.