EVM-666: Fix eth_getLogs index issue

[goran-ethernal]

Description

This PR fixes issue where eth_getLog rpc call did not return correct values for LogIndex for block logs.

Before, the LogIndex field was set by transaction instead of block. For example, if block had two transactions with two logs each, the call would return log indexes: 0, 1, 0, 1, instead of: 0, 1, 2, 3.

This PR added a UT for this.

Changes include

• Bugfix (non-breaking change that solves an issue)
• Hotfix (change that solves an urgent issue, and requires immediate attention)
• New feature (non-breaking change that adds functionality)
• Breaking change (change that is not backwards-compatible and/or changes current functionality)

Checklist

• I have assigned this PR to myself
• I have added at least 1 reviewer
• I have added the relevant labels
• I have updated the official documentation
• I have added sufficient documentation in code

Testing

• I have tested this code with the official test suite
• I have tested this code manually

[rzmahmood]

Just confirming, this will fix for logs returned by both eth_getLogs and eth_getBlockByNumber?

[Stefan-Ethernal]

LGTM

[Stefan-Ethernal]

Just confirming, this will fix for logs returned by both eth_getLogs and eth_getBlockByNumber?

AFAIK, the eth_getBlockByNumber endpoint does not return logs. So this PR affects the eth_getLogs and eth_getFilterLogs endpoints.

[vcastellm]

LGTM