If the "gnosis_block_hotfix" feature flag is enabled, use the Gnosis-compatible representation of the proposal when calculating its hash tree root.  This should fix Gnosis proposals failing due to bad signature.

category: feature
ticket: #3181
feature_flag: gnosis_block_hotfix

* Added `chiado` network spec in addition to the existing `gnosis`.
* Feature `gnosis_block_hotfix` is enabled automatically when gnosis | chiado network is detected.
* When the user explicitly disables `gnosis_block_hotfix` feature, the app just yields warning during startup:

```
Feature gnosis_block_hotfix is required by gnosis/chiado, but explicitly disabled
```

category: feature
ticket: none
feature_flag: gnosis_block_hotfix

- fix test peers on timeout, sometimes it went in the case where the current context is done, but the result of the currently running test wasn't sent to the channel
- fix wrongly named variables

category: test
ticket: none

Fixing flaky test in previous PR #3267 revealed another issue. Fixing that one, which is purely unit test related.

category: test
ticket: none

After #3267 was merged, on `ctx.Done()` we push the latest unfinished test. This causes out of range in the outer function in some ocassions.

category: bug
ticket: none

Compose tests were failing because of `docker-compose` command hasn't been changed to `docker compose` on some places and the version on top wasn't removed.

category: test
ticket: none