new schains created on same ports as removed schains

[sync-by-unito[bot]]

new schain cannot be started when she was created on same ports as removed schain versions: schain:3.7.1-develop.7 admin:2.0.0-develop.36 STR:

1. create 6+ MEDIUM schains
2. remove them
3. create 6+ MEDIUM schains expected: all schains containers works and all schains block mining actual: some of schains container cannot run because of Error creating SkaleHost — ZmqBroadcaster: Address already in use tcp://0.0.0.0:10389

sChains on contracts: ['', 'beautiful-saiph', 'harsh-alsciaukat', 'attractive-al-anz', 'glamorous-almaak', 'screeching-muliphen', 'rapping-enif']
sChains on node: ['attractive-al-anz', 'beautiful-saiph', 'elegant-skat', 'faint-dschubba', 'glamorous-almaak', 'handsome-izar', 'harsh-alsciaukat', 'hissing-alcor', 'noisy-gomeisa', 'noisy-shedir', 'plain-dsiban', 'rapping-enif', 'screeching-muliphen', 'tinkling-fum-al-samakah', 'whispering-cor-caroli']
[2021-06-07 16:28:03,692 WARNING] - 1179 - MainThread - core.schains.cleaner:110 - sChain elegant-skat was found on node, but not on contracts: ['', 'beautiful-saiph', 'harsh-alsciaukat', 'attractive-al-anz', 'glamorous-almaak', 'screeching-muliphen', 'rapping-enif'], going to remove it!

┆Issue is synchronized with this Jira Bug ┆Attachments: admin_52.11.161.79.txt

[sync-by-unito[bot]]

➤ Ganna Kulikova commented:

The issue is reproduced when the cleaner procedure for the previous schain has not completed (edge case scenario)

Not critical for IMA release

[sync-by-unito[bot]]

➤ Automation for Jira commented:

Corresponding Pull Request https://github.com/skalenetwork/skale-consensus/pull/504

[sync-by-unito[bot]]

➤ Automation for Jira commented:

Corresponding Pull Request https://github.com/skalenetwork/skale-consensus/pull/505

[sync-by-unito[bot]]

➤ Automation for Jira commented:

Corresponding Pull Request https://github.com/skalenetwork/skale-consensus/pull/506