Block finalization time on archive node is 5x slower than on core nodes during significant load

[oleksandrSydorenkoJ]

Describe the bug
Reproducible only with 200-250 mill gas usage.

Preconditions:
Skale chain with connected archival node
Address A with contract deployment role and 5 Sfuel on balance

Versions
skalenetwork/schain:3.18.0-develop.17 - core nodes
skalenetwork/schain:3.17.2-develop.3-historic - archival node

To Reproduce

1. Deploy the contract to store data to state
2. Send 1000 transactions of storing data on blockchain, every block gas usage should be at least 200 mil
3. Check block finalization time on the core node
4. Check block finalization time on the archival node
5. Compare results from step 3 and step 4

Expected behavior
Block finalization time on core and archival node should be the same

Actual state:
Block finalization time on Core node is 1-2 seconds, and 10-11 on archival node

Core node:

2024-01-05 16:51:44.502881   Block 7014 DB usage is 6310. Piece DB usage is 9500909 bytes
2024-01-05 16:51:44.503751   SWT:1053:BFT:1527

Archival node

2024-01-05 16:56:53.904277   Block 7014 DB usage is 6310. Piece DB usage is 9500909 bytes
2024-01-05 16:56:53.905577   SWT:5926:BFT:5938

[olehnikolaiev]

probably related to the high amount of time consumed by skaled to commit transaction into the historic state db and to the #1870