Improve visibility around poet registrations in events

[poszu]

Description

Users need a better UX around poet registrations to help them understand the process of registration in poet services and querying proofs.

Acceptance Criteria

Add new events saying:

• created poet client (URL)
• registered in poet (URL, challenge, round)
• got proof from poet (URL, round, ticks)
• selected best poet proof (URL, round, ticks)

[reythia]

Great to see this getting some love from core devs!

Based on feedback and questions users raise on T24, might I also suggest considering:

• Cycle gap open for n hrs Reassures users that the node "knows" the CG is open and is operating correctly / on the same basis as user expects. Useful for people switching between shifts + gaps.

• Not generating proof because... Many users still don't understand the circumstances of registration only and assume something is wrong. The 'waiting for registration' event still has users asking why and is it broken.

• Node failed to register with poet in time Just another one for managing user expectations - negative confirmation can be as useful as positive confirmation.