Kusama node crashes with `oom`

## Describe the bug

- The staging Kusama Gossamer node is facing an `oom` problem which kills the node around the block `#1880576`, as we can see in the image the number of tries in memory grows and is not pruned at any time.

- Also the Kusama node is not finalizing any block since block `#1492283`

```
2023-10-04T16:55:13Z INFO 🚣 currently syncing, 8 peers connected, 8 available workers, target block number 19966068, finalised block number 1492283 with hash 0x01e94e1e7e9cf07b3b0bf4e1717fce7448e5563901c2ef2e3b8e9ecaeba088b1 pkg=sync
```

- The problem with finalization might be related to these errors `authority is not in set` that appear in the logs

```
2023-10-04T16:52:33Z ERROR block data processing for block with hash 0xf43ae4910bfac35778e8a9d8cc47c183151d092deadcce2257cbc6499a558e22 failed: handling justification: verifying block number 1880359 justification: authority is not in set pkg=sync

2023-10-04T16:52:33Z ERROR requesting max blocks from best block header: while handling workers results: while handling ready block: handling justification: verifying block number 1880359 justification: authority is not in set pkg=sync
```

- Every time an error like this appears is related to a block with a justification that should be finalized to prune the trie from the memory