Scoru: multiple rollup-nodes with different operators leads to inconsistencies between stakers and their commitments

Whenever two rollup-nodes are initiated for a given rollup address with two different operators with enough stake, the first one that is launched afterwards seems to recover properly and is able to stake properly on a commitment but the second seems to recover properly as well from the rollup-node perspective but if we're trying to retrieve information from the context to see which staker is staking on which commitment we can witness inconsistencies since the second operator does not show at all.

To check that, the rpcs that were used were:

• /chains/main/blocks/head/context/sc_rollups/sc_rollup/<sc_rollup_address>/stakers_commitments
• /chains/main/blocks/head/context/sc_rollups/sc_rollup/<sc_rollup_address>/staker/<staker_id>/staked_on_commitment

An other information that can help, the operations commited from the potential second staker do not appear at all in the mempool, the problem seems to be somehow related to the rollup-node itself.