Goal: Include event tracking at TN

(issue description to be improved and specs created)

Blockchains' smart contract events are usually good to enable indexers to populate data correctly and efficiently.

Scanning the entire network for existing data is inefficient, and we have workarounds to scan data incrementally for structural changes (i.e. new streams), but we could do better to track other important events for our indexer.

• taxonomy updates
• stream deletes
• metadata updates (visibility, permissions, etc)

Finding the correct granularity is not easy; we'd need to understand the impact on each event tracking, but it could make our indexer's job a lot more efficient.

for this we'd need a new table for events, and at our write actions execute some private dispatch_event action

No files or tests are named. Start by defining the event-tracking specifications and reviewing the indexer's current incremental scanning workarounds, then assess the proposed events: taxonomy updates, stream deletes, and metadata updates. Done should include agreed event granularity and a clear design for the events table and dispatching from write actions.