Prioritize BLS signatures from APIs

[twoeths]

Problem description

When gossip blocks are late, node has to download block through beacon_block_by_root

gossip attestations have to be reprocessed at the same time which send too many signature sets to bls worker thread pool, job length is consistently at >= 500

which cause bls job wait time to be very high during that time

which cause sumitPoolAttestations time to be very high too

the submission was late so attestations are not included in any AggregateAndProof (below is timely_target_no_aggregate_inclusion type in attestation performance summary panel)

Solution description

root cause of the issue is gossip performance, however we could prioritize verifying bls signatures from submitPoolAttestations api

with #5734, it should take <7ms per slot to validate 64 signature sets of same attestation data, we could consider verifyOnMainThread option for submitPoolAttestations api

Additional context

No response

[twoeths]

this is also related to #5416 where we can filter api attestations of the same attestation data and validate them in batch in order to use new api in #5734

[twoeths]

an alternative would be to insert to the jobs queue of worker pool at index 0 instead of to append to it