Inconsistent CRO merge behavior

[magnified103]

Steps to reproduce:

• Checkout the tree https://github.com/topology-foundation/ts-topology/tree/bugfix/inconsistent-merge

cd ts-topology/examples/chat
yarn
yarn build
pnpm exec tsx tests/index.test.ts

Result:

topology::network ::broadcastMessage: Error: PublishError.NoPeersSubscribedToTopic
    at @chainsafe/libp2p-gossipsub.publish (/Users/magnified/projects/ts-topology/node_modules/@chainsafe/libp2p-gossipsub/src/index.ts:2263:13)
    at async TopologyNetworkNode.broadcastMessage (file:///Users/magnified/projects/ts-topology/packages/network/dist/src/node.js:172:13)
merging vertex b9fcd76b07784ba73d4e8d59741ea8508f7656346f0c40d2c837b13a275b26df
merged vertex b9fcd76b07784ba73d4e8d59741ea8508f7656346f0c40d2c837b13a275b26df
merging vertex 02465e287e3d086f12c6edd856953ca5ad0f01d6707bf8e410b4a601314c1ca5
merged vertex ee075937c2a6c8ccf8d94fb2a130c596d3dbcc32910b6e744ad55c3e41b41ad6
^C

Behavior: one node tries to merge the root hash 02465e287e3d086f12c6edd856953ca5ad0f01d6707bf8e410b4a601314c1ca5 during the sync, and it creates a stale vertex ee075937c2a6c8ccf8d94fb2a130c596d3dbcc32910b6e744ad55c3e41b41ad6 during that process.