DAL/Node: accuser: register the traps on the fly and inject the entrapment evidence

What

Alternative to !16223 (closed) where we now register the traps when

• the shard data is received as a gossipsub message
• the shard data is published as a gossipsub message

before injecting the entrapment evidence in the DAL node daemon.

Why

The implementation is simpler than the original proposal.

As mentioned in %DAL: baker incentives (part 4: accuser and testing) , it is the responsibility of the DAL node to accuse a malicious baker. This MR is part of it.

How

• Add a cache for traps in the DAL node store
• Populate the cache when a new shard is as a trap
• Inject the accusation in the daemon loop

Manually testing the MR

Checklist

• Document the interface of any function added or modified (see the coding guidelines)
• Document any change to the user interface, including configuration parameters (see node configuration)
• Provide automatic testing (see the testing guide).
• For new features and bug fixes, add an item in the appropriate changelog (docs/protocols/alpha.rst for the protocol and the environment, CHANGES.rst at the root of the repository for everything else).
• Select suitable reviewers using the Reviewers field below.
• Select as Assignee the next person who should take action on that MR