feat(consensus): global substates in dedicated shard

[ksrichard]

Description

We reserve a specific shard (0) for all the global substates, so regardless of which shard it would be in calculated from it's address, we use the hardcoded shard.

Motivation and Context

When a node loses all of its data or behind a lot the tip of chain, then it synchronizes the chain, but in this case we do not have the templates all the time as a substates as it is not guaranteed that templates shard is falling into the shard group's range (where the actual VN is).

How Has This Been Tested?

Scenarios

New VN added to swarm

1. Start a local swarm with 15 members
2. Create a new account in DAN wallet (http://127.0.0.1:12038/ in this setup)
3. Deploy a new template to the local network
   Using CLI (example):

$ tari deploy --account acc counter -y                                                                                                                                                                                                                                                                                      
✅ Init configuration and directories
✅ Refresh project templates repository
✅ Refresh wasm templates repository
✅ Building WASM template project "counter"
✅ Deploying project "counter" to local network
⭐ Your new template's address: 443c620320c79aa3ed89f559f54a42986718b0c7089bddcc3561b5efed06da13

4. Check if template presents on VNs (just check some randomly from both committees)
5. Add a new VN by clicking Add VN on swarm UI (http://127.0.0.1:8080/)
6. Mine (using Mine button on the same UI on top) until new epoch and new VN is available
7. Check if the template is synced to the new VN

VN gets out of sync / loose data

1. Start a local swarm with 15 members
2. Create a new account in DAN wallet (http://127.0.0.1:12038/ in this setup)
3. Deploy a new template to the local network
   Using CLI (example):

$ tari deploy --account acc counter -y                                                                                                                                                                                                                                                                                      
✅ Init configuration and directories
✅ Refresh project templates repository
✅ Refresh wasm templates repository
✅ Building WASM template project "counter"
✅ Deploying project "counter" to local network
⭐ Your new template's address: 443c620320c79aa3ed89f559f54a42986718b0c7089bddcc3561b5efed06da13

5. Check if template presents on VNs (just check some randomly from both committees)
6. Select a VN which is not in the 0-X shard group and make sure the template presents as well on the VN
7. Mine until next epoch
8. Delete data of the VN by clicking on Delete Data button at the VN (it will stop the VN as well)
9. Start VN again and check if it catches up and contains the template

What process can a PR reviewer use to test or verify this change?

Breaking Changes

• None
• Requires data directory to be deleted
• Other - Please specify

[github-actions]

Test Results (CI)

619 tests  +25   610 ✅ +16   3h 36m 19s ⏱️ + 2h 3m 17s
 68 suites +13     0 💤 ± 0 
  2 files   + 1     9 ❌ + 9 

For more details on these failures, see this check.

Results for commit 794c646. ± Comparison against base commit ddc4632.

♻️ This comment has been updated with latest results.