Fix missing prune log index

[somnathb1]

Existing prune had some confusing logic (thanks to me).

In PR, change the logic to:
if receipt, or any individual log in the receipt contains an address in noPruneContracts the entire log must be stored and indexed.

Also fixes a regression that logs were not getting indexed - this was due to

if l.BlockNumber < pruneBlock && cfg.noPruneContracts != nil && !cfg.noPruneContracts[l.Address] {

Since the individual log object didn't have the block number - something that shouldn't matter.
In PR, change the logic to:
Use blockNum from outer loop

[tolbrino]

@somnathb1 Does this change require an Erigon node to re-sync entirely for the index to be generated properly?

[somnathb1]

This will go in the next release notes too:

2 suggestions alongside to improve database space usage and indexing.
Stop the node, upgrade thorax/erigon:devel docker image. Then

integration stage_log_index --reset --datadir=<your_datadir>

Then restart and let it sync to the tip.

Optional: Improve disk usage
Stop the node and

mdbx_to_mdbx --chaindata=<your_datadir>/chaindata --chaindata.to=<your_datadir>/chaindata2 --datadir=<any_random_location_for_temp_files>
mv chaindata chaindataOld
mv chaindata2 chaindata

Then restart. The new chaindata should be about 1/2 - 1/3 of the size of the old (Bonus!). If all goes well, you can delete chaindataOld

To do the extra commands with docker image, you can always do

docker run -it -v <your_datadir>:/data --entrypoint sh thorax/erigon:devel


Then the value of datadir for integration and mdbx commands is /data on the docker shell, where you can run the above.
Also, just a reminder, 2.58 originally synced node cannot see much benefit on upgrading (it was also in the release notes of 2.59) The above suggestion would work when upgrading from 2.59.x