logs: analyzer-v2

[iurii-ssv]

Existing analyzer is analyzing logs to gather some specific stats or answer a very specific questions (like how many times SSV node crashed due to loss of connectivity with CL/EL). While this kind of info is useful it doesn't always help us answer the question of "what went wrong with a particular duty".

This PR implements a somewhat different kind of analyzer (call it analyzer-v2) that spits out:

• a detailed duty breakdown for a particular duty to show which "milestones" are reached and at what times relative to slot start (currently duty is identified by duty-type + slot-number)
• add filtering by duty-id to identify duty more precisely (vs duty-type + slot-number that can spit out lots of data)
• any unexpected errors encountered (filtering out "expected" errors that are not really critical to duty execution)