[fix] #4140: Fix registration of new peer

[mversic]

Description

• Fixed new peer registration
• Fixed peer restart

Linked issue

Closes #4140

Benefits

Checklist

• I've read CONTRIBUTING.md
• I've used the standard signed-off commit format (or will squash just before merging)
• All applicable CI checks pass (or I promised to make them pass later)
• (optional) I've written unit tests for the code changes
• I replied to all comments after code review, marking all implemented changes with thumbs up

[coveralls]

Pull Request Test Coverage Report for Build 7193927722

• 51 of 65 (78.46%) changed or added relevant lines in 10 files are covered.
• 7105 unchanged lines in 125 files lost coverage.
• Overall coverage decreased (-3.3%) to 56.119%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
core/src/block.rs	17	18	94.44%
core/src/sumeragi/mod.rs	0	1	0.0%
core/test_network/src/lib.rs	0	1	0.0%
p2p/src/network.rs	0	1	0.0%
smart_contract/executor/derive/src/validate.rs	3	4	75.0%
core/src/sumeragi/main_loop.rs	2	11	18.18%

Files with Coverage Reduction	New Missed Lines	%
config/base/derive/src/view.rs	1	99.37%
core/src/smartcontracts/isi/block.rs	1	87.5%
ffi/src/option.rs	2	71.43%
config/src/genesis.rs	3	72.92%
config/src/logger.rs	3	92.68%
data_model/derive/src/has_origin.rs	3	95.16%
data_model/src/events/execute_trigger.rs	3	30.77%
data_model/src/peer.rs	3	47.62%
ffi/src/ir.rs	3	80.0%
ffi/src/lib.rs	3	93.46%

Totals
Change from base Build 5423219773:	-3.3%
Covered Lines:	22783
Relevant Lines:	40598

---

💛 - Coveralls

[Erigara]

I wounder how we should deal with more general case when whole topology changed.

Step by step:

1. Network is started with peer set A
2. After some height peer set A is replaced with peer set B (A intersection B = empty set)
3. New peer is added with trusted peers peers from set B
4. Peer get block and update it's topology to set A (because at this height only peers from topology A were present)

[mversic]

I wounder how we should deal with more general case when whole topology changed.

good point. We should discuss the best solution in a separate ticket. Created #4145