Block execution time grows with the count of transactions

[oleksandrSydorenkoJ]

Note
Probably, can fix or improve #1962

Describe the bug
Related to #526
Execution algorithm of transactions: After validation, a transaction is added to a List and executed there. When a new transaction is added to the List, it is not only the most recently added transaction that gets executed but all transactions present in the list. Therefore, as the number of transactions increases, the execution time grows disproportionately

Versions
Skaled:3.20.0-beta.1

Preconditions
Schain medium type
1000 Accounts with sFuel on balance
tool for running performance tests

To Reproduce

1. Run performance tests with 100 transactions in a block
2. Check block execution time (BFT, SWT, and CWT values) and save the SWT for 100 txs
3. Increase the number of transactions in the block up to 1000
4. Check block execution time (BFT, SWT, and CWT values) and save the SWT for 1000 txs

Expected behavior
SWT for the block with 1000 transactions should take 10 times more time than the block with 100 txs in a linear way

Actual state
SWT for the block with 1000 transactions is slower than a block with 100 txs almost in 40 times (40 ms to 1600ms in average)