[Backwards-compatibility, v1.x.x-specific] Re-enable thorchain-mainnet-v1 sync from genesis

Multipartiterequested to merge
Multi/fix-v1-sync-from-genesis into develop

[Specific to thorchain-mainnet-v1, changes not to be merged for post-hard-fork thorchain-mainnet-v2 (>= v2.135.0) branch]

This is intended to close #2028 (closed)
'[Backwards-compatibility] Pre-hard-fork initGenesis SetRUNEPool breaks thorchain-mainnet-v1 sync from genesis',
however likely please either inform of a different branch to target or else use this MR's two commits directly,
as it should be used for a v1.134.x patch rather than the develop branch's v2.135.0 .

Pipeline failure of this MR for the develop branch is expected in reference to the develop branch's v2.135.0 hard fork changes.

The 'V134 disclosures' commit 9a4b5713 displayed is not a suggested commit to add, as it is already the tip commit of v1.134.0:
https://gitlab.com/thorchain/thornode/-/commits/v1.134.0

Though there is no reason to merge this for a v2.135.0 branch, for reference this is the passed pipeline for if after a develop-branch rebase:
https://gitlab.com/thorchain/thornode/-/commits/ee57c000
https://gitlab.com/thorchain/thornode/-/pipelines/1415913608

I label this Priority 1 rather than Priority 2 as it has already affected others trying to sync thorchain-mainnet-v1.

Edited by Multipartite

Merge request reports