Fix for fork handling issues

[piotrkosecki]

There were three problems:

1. Not consistent invalidation - when the fork information was inserted the DB was checking immediately for foreign keys and that was breaking it because it should wait till the end of transaction. Those changes in schema fixed this issue:

DEFERRABLE INITIALLY DEFERRED;

2. Duplicate error when invalidating tables - problem was when one of the blocks was previously invalidated and had the same or greater block level than current invalidation(it can happen when for example node is not consistent with replacing blocks and first changes block that was higher and then changes lower block). Fix for this is to invalidate only entries with leader/Main fork_id. This fixes the issue:

.filter(x => levelColumn(x) >= fromLevel && forkIdColumn(x) === Fork.mainForkId)

3. Starting from the old head. After fork invalidation we were using the same hade as before the invalidation. Meaning we would continue fetching blocks like nothing happened and we would have big hole in the valid blocks. This fixes it:

maxLevelNew <- indexedData.fetchMaxLevel

Also I've added more logging and set fork handling to true by default.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication