Align events implementation with FIP-0049

[raulk]

• Stop flushing events to blockstore when message execution concludes.
• Ensure that the events field in ApplyRet is populated with the list of events in the correct order.
• Ensure that the events field is correctly propagated through the FFI boundary. This requires an integration test in Lotus.
• Redesign the events system in Lotus to consume events from the in-memory list instead of loading them from the blockstore. Write events to the blockstore when Eth API is enabled.
• Rearchitect gas charges as per FIP-0049.
• Finish validation logic and validate that values are CBOR Major Type 2 (byte strings).
• Ethereum: use compact key names as per example in FIP-0049 (and soon FIP-0054 spec).
  • Propagate this change to the Lotus events system.
• fix: event filters use cbor encoding internally lotus#10085 (comment)

PRs

Beta Give feedback

1. EVM: LOG{0..4}: adjust event definitions as per FIP-0054. builtin-actors#1057
   +0
2. Align events implementation with FIP-0049 #1481
   +0
3. feat: evm: align events implementation with FIP-0049 and FIP-0054. lotus#10152
   +0

[raulk]

Finish validation logic and validate that values are CBOR Major Type 2 (byte strings).

We currently deserialize the event object and retain it in memory. Also, the current schema types values as RawBytes. Therefore, both these points are addressed. There is no extra validation logic needed. Ideally we would validate without desrializing, but that's not even beneficial now because to fully benefit from zero-copy, we'd need the AMT implementation to cooperate by taking trusted CBOR bytes, which it doesn't.