Wrong id in log objects when using getPastLogs API

[JosephK95]

trafficstars

Description

When we execute getPastLogs API, it seems that Besu returns wrong value for the id field in every returned log object. The same thing happens when using getTransactionReceipt API.

Steps to Reproduce (Bug)

1. Download the following file and untar it: test_log_id.tar.gz
2. Execute Besu binary with the following flags: besu --data-path test_log_id/data-besu --genesis-file test_log_id/besu.json --rpc-http-port 8549 --rpc-http-enabled --rpc-http-api ETH --network-id 15 --discovery-enabled false
3. Execute the test case file: node test1.js

Expected behavior: All other client implementations return the following result:

[{..., "id": "log_e92989bc"},
 {..., "id": "log_f02e3690"},
 {..., "id": "log_2312ee27"},
 {..., "id": "log_deff5d41"}, 
 {..., "id": "log_0d27fabe"}, ...] 

Actual behavior: Only Besu returns the following result:

[{..., "id": "log_207bb0d1"},
 {..., "id": "log_f02e3690"},
 {..., "id": "log_840ba6f4"},
 {..., "id": "log_3a16747a"}, 
 {..., "id": "log_1344d910"}, ...] 

Frequency: Always

Versions (Add all that apply)

• Software version: besu/v22.4.4/linux-x86_64/openjdk-java-16
• OS Name & Version: Ubuntu 20.04.4 LTS
• Node.js / web3.js Versions: v16.15.0 / v1.7.3