Event index should be unique for tipsets

[aarshkshah1992]

Related Issues

Closes #11630

Proposed Changes

The event index for logs should be unique for all events in the same tipset to confirm with geth behaviour.

Additional Info

Checklist

Before you mark the PR ready for review, please make sure that:

• Commits have a clear commit message.
• PR title is in the form of of <PR type>: <area>: <change being made>
  • example: fix: mempool: Introduce a cache for valid signatures
  • PR type: fix, feat, build, chore, ci, docs, perf, refactor, revert, style, test
  • area, e.g. api, chain, state, market, mempool, multisig, networking, paych, proving, sealing, wallet, deps
• If the PR affects users (e.g., new feature, bug fix, system requirements change), update the CHANGELOG.md and add details to the UNRELEASED section.
• New features have usage guidelines and / or documentation updates in
  • Lotus Documentation
  • Discussion Tutorials
• Tests exist for new functionality or change in behavior
• CI is green

[rvagg]

👌 yep, looks good, except for the migration concern, will take that discussion to Slack

[rvagg]

Approving without running it. If this works on calibnet and you manually inspect the DB and see the migration worked then all good. The rest looks good.

[aarshkshah1992]

Tested this on calibnet

SELECT a.event_index, b.event_index FROM event a INNER JOIN event b ON a.tipset_key_cid = b.tipset_key_cid WHERE a.id != b.id LIMIT 120;

This query returns rows with duplicate event_indexes for master but does NOT do so for the current branch and returns sequential event_indices instead

4|0
4|1
4|2
4|3
4|5
4|6
4|7
4|8
4|9
4|10
4|11
4|12
4|13
4|14
4|15
5|0
5|1
5|2
5|3
5|4
5|6
5|7
5|8
5|9
5|10
5|11
5|12
5|13
5|14
5|15
6|0
6|1
6|2
6|3
6|4
6|5
6|7
6|8

......