Feature/orc 428 ejector check events public keys

[chasingrainbows]

Description

1. Events pubkeys checking on CL added
2. Add batching logic to src/services/job-processor/service.ts, to reduce CL requests amount
3. VOTING_EVENTS_FRAME_BLOCKS added + pre-uploading of voting-based events
4. Fixed minor bug when aragon voting have been ignored if easy track address is not set up

Related Issue/Task

• Related task: orc-428

How Has This Been Tested?

Describe how you tested the changes:

• Local tests (e.g., pytest)
• Manual testing (describe steps)
• Not tested (explain why)

Checklist

• Documentation updated (if required)
• New tests added (if applicable)

[eddort]

Good job! I suggest moving the validator loading logic to a single place to unify the logic for checking public keys, metrics for withdrawn validators, remaining messages, and the isExiting check.

[eddort]

There’s a subtle issue in the way event proofs are calculated. The logic currently assumes that the entire relevant event window fits within toBlock - ORACLE_FRAME_BLOCKS, which holds for oracle submission proofs, but might not be valid for EasyTrack or Aragon voting proofs.

We should double-check the actual block range between vote creation and execution in those cases and verify that it consistently falls within the toBlock - ORACLE_FRAME_BLOCKS window. If not, we may need to adjust the logic or make the proof window configurable per use case.