[fix] #0000: On-chain predictable iteration order

[mversic]

Description

• replace all HashMap/HashSet in iroha_core with IndexMap/IndexSet
• add HashMap/HashSet to dissallowed_types

Linked issue

Closes #3

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 7179205152

• 9 of 19 (47.37%) changed or added relevant lines in 8 files are covered.
• 7095 unchanged lines in 130 files lost coverage.
• Overall coverage decreased (-3.2%) to 56.221%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
core/src/sumeragi/view_change.rs	0	1	0.0%
core/src/sumeragi/mod.rs	0	4	0.0%
core/src/smartcontracts/isi/triggers/set.rs	3	8	37.5%

Files with Coverage Reduction	New Missed Lines	%
config/base/derive/src/view.rs	1	99.37%
config/src/block_sync.rs	1	95.0%
config/src/network.rs	1	93.75%
config/src/torii.rs	1	95.45%
config/src/wasm.rs	1	87.5%
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%

Totals
Change from base Build 5423219773:	-3.2%
Covered Lines:	23055
Relevant Lines:	41008

---

💛 - Coveralls

[Arjentix]

In the issue you wrote that you'll use BTree* collections. Why did you change your mind?

[mversic]

In the issue you wrote that you'll use BTree* collections. Why did you change your mind?

it seemed as a more natural replacement. As long as the bug is fixed we can always switch to b-trees.

[Arjentix]

So index at the end