Fix bugs

[Neylix]

Description

Fix some bugs

• Uncatched error in Replication while fetching previous transaction causing replication crash
• When writing a transaction chain in DB, remove ALL transaction of this chain from KOLedger
• To calculate node availabilty we use a wheighted average to increase recent slot weight, but the slot list was not sorted so the wheight was not applied to the expected slot
• Ecto crash when having error somewhere (i.e content oversized) and the transaction contains ownerships
• Since the GetTransactionChain message can return in asc or desc order, the conflict resolver was not accurate :

let's asume a chain TX1 -> TX2 -> TX3 -> TX4 -> TX5 -> TX6 -> TX7 and the nb of tx returned is 5 by request in desc order
if a node didn't replicate the last transaction we could have a result like
node1 :

%{
  transactions: [TX6, TX5, TX4, TX3, TX2],
  more?: true,
  paging_state: TX2
}

node2 :

%{
  transactions: [TX7, TX6, TX5, TX4, TX3],
  more?: true,
  paging_state: TX3
}

node3: same as node2

The good return is node2 and node3 result, but as node1 and other have more? at true and length of transactions list is the same, so the previous conflict resolver take the first element of the returns list which can be node1 with the wrong result.
So to fix this I added a sort on the timestamp of the first transaction of the list (regarding the order requested)

Type of change

• Bug fix (non-breaking change which fixes an issue)

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules