[Version-unspecific] queryMimirV2IDs: jsonify the map for a deterministic sorted order

[Version-unspecific]

Intended to close #1770 (closed)
'queryMimirV2IDs alone has arbitrary order which causes test-regression pipeline job failures'.

---

Initial commit job failure notes:
Other than the many empty operation warnings,
the order is as intended,
but the response appears in a {} object (like /thorchain/mimir ) rather than a [] array,
and so .[0] produces Cannot index object with number.
The regression test asserts thus may need to be changed to the format .|[.[]][0].id rather than .[0].id .
."1-GLOBAL".id would also pass, but would work regardless of order and so not reflect the fixed order determinism for #1770 (closed)'s resolution.

12:28PM INF cmd/run.go:35 > Running regression test: suites/mimir/mimir_v2.yaml
12:28PM WRN cmd/run.go:172 > empty operation, line numbers may be wrong
12:28PM WRN cmd/run.go:172 > empty operation, line numbers may be wrong
12:28PM WRN cmd/run.go:172 > empty operation, line numbers may be wrong
12:28PM WRN cmd/run.go:172 > empty operation, line numbers may be wrong
12:28PM WRN cmd/run.go:172 > empty operation, line numbers may be wrong
12:28PM WRN cmd/run.go:172 > empty operation, line numbers may be wrong
12:28PM INF cmd/run.go:205 > >>> [1] state line=0
12:28PM INF cmd/run.go:306 > Executing 26 operations
12:28PM INF cmd/run.go:308 > >>> [2] create-blocks line=3
12:28PM INF cmd/run.go:308 > >>> [3] tx-mimir line=6
12:28PM INF cmd/run.go:308 > >>> [4] check line=12
12:28PM INF cmd/run.go:308 > >>> [5] tx-mimir line=17
12:28PM INF cmd/run.go:308 > >>> [6] tx-mimir line=21
12:28PM INF cmd/run.go:308 > >>> [7] tx-mimir line=26
12:28PM INF cmd/run.go:308 > >>> [8] create-blocks line=31
12:28PM INF cmd/run.go:308 > >>> [9] check line=36
12:28PM INF cmd/run.go:308 > >>> [10] check line=39
12:28PM INF cmd/run.go:308 > >>> [11] check line=44
12:28PM INF cmd/run.go:308 > >>> [12] tx-mimir line=49
12:28PM INF cmd/run.go:308 > >>> [13] create-blocks line=59
12:28PM INF cmd/run.go:308 > >>> [14] check line=62
12:28PM INF cmd/run.go:308 > >>> [15] check line=67
12:28PM INF cmd/run.go:308 > >>> [16] tx-mimir line=70
12:28PM INF cmd/run.go:308 > >>> [17] create-blocks line=75
12:28PM INF cmd/run.go:308 > >>> [18] check line=80
Operation:
type: check
endpoint: http://localhost:1317/thorchain/mimirV2/ids
params: {}
status: 200
asserts:
    - .[0].id == 1
    - .[0].name == "AFFILIATEFEEBASISPOINTSMAXGLOBAL"
    - .[0].legacy_key == "MAXAFFILIATEFEEBASISPOINTS"
    - .[0].vote_key == "1-GLOBAL"
    - .[0].type == "Economic"
    - .[0].votes."500" == 4
    - .[1].id == 2
    - .[1].name == "BONDPAUSEGLOBAL"
    - .[1].legacy_key == "PAUSEBOND"
    - .[1].vote_key == "2-GLOBAL"
    - .[1].type == "Operational"
    - .[1].votes."1" == 1
Failed Assert: .[0].id == 1
Endpoint Response:
{
  "1-GLOBAL": {
    "id": 1,
    "name": "AFFILIATEFEEBASISPOINTSMAXGLOBAL",
    "vote_key": "1-GLOBAL",
    "legacy_key": "MAXAFFILIATEFEEBASISPOINTS",
    "type": "Economic",
    "votes": {
      "500": 4
    }
  },
  "2-GLOBAL": {
    "id": 2,
    "name": "BONDPAUSEGLOBAL",
    "vote_key": "2-GLOBAL",
    "legacy_key": "PAUSEBOND",
    "type": "Operational",
    "votes": {
      "1": 1
    }
  }
}
jq: error (at <stdin>:21): Cannot index object with number

test/regression/suites/mimir/mimir_v2.yaml

@@ -17,7 +17,6 @@ asserts:
 # check two conditions:
 # 1) 3-node V2 majority cannot set an economic mimir (e.g. 1-GLOBAL)
 # 2) 3 out of 5 nodes (60%, minority) cannot set an economic mimir (according to previous node mimir rules)
----
 type: tx-mimir
 key: "1-GLOBAL"
 value: 500
@@ -58,7 +57,6 @@ asserts:
 ---
 # check that 4 node accounts (80%) can set an econimic mimir
 # in effect, ensure that we are still honoring old node mimir logic
----
 type: tx-mimir
 key: "1-GLOBAL"
 value: 500
@@ -83,7 +81,6 @@ asserts:
   - . == 500
 ---
 # check that 3 node accounts (mimir v2) can set an operational mimir (e.g. 2-GLOBAL)
----
 type: tx-mimir
 key: "2-GLOBAL"
 value: 1
@@ -93,25 +90,23 @@ type: create-blocks
 count: 1
 ---
 # once the vote has started, the id mapping should populate
----
 type: check
 endpoint: http://localhost:1317/thorchain/mimirV2/ids
 asserts:
-  - .[0].id == 1
-  - .[0].name == "AFFILIATEFEEBASISPOINTSMAXGLOBAL"
-  - .[0].legacy_key == "MAXAFFILIATEFEEBASISPOINTS"
-  - .[0].vote_key == "1-GLOBAL"
-  - .[0].type == "EconomicMimir"
-  - .[0].votes."500" == 4
-  - .[1].id == 2
-  - .[1].name == "BONDPAUSEGLOBAL"
-  - .[1].legacy_key == "PAUSEBOND"
-  - .[1].vote_key == "2-GLOBAL"
-  - .[1].type == "OperationalMimir"
-  - .[1].votes."1" == 1
+  - .|[.[]][0].id == 1
+  - .|[.[]][0].name == "AFFILIATEFEEBASISPOINTSMAXGLOBAL"
+  - .|[.[]][0].legacy_key == "MAXAFFILIATEFEEBASISPOINTS"
+  - .|[.[]][0].vote_key == "1-GLOBAL"
+  - .|[.[]][0].type == "EconomicMimir"
+  - .|[.[]][0].votes."500" == 4
+  - .|[.[]][1].id == 2
+  - .|[.[]][1].name == "BONDPAUSEGLOBAL"
+  - .|[.[]][1].legacy_key == "PAUSEBOND"
+  - .|[.[]][1].vote_key == "2-GLOBAL"
+  - .|[.[]][1].type == "OperationalMimir"
+  - .|[.[]][1].votes."1" == 1
 ---
 # send in two more votes
----
 type: tx-mimir
 key: "2-GLOBAL"
 value: 1
@@ -141,7 +136,6 @@ asserts:
   - . == 1
 ---
 # check that an operation mimir can be unset by removing 1 vote
----
 type: tx-mimir
 key: "2-GLOBAL"
 value: -1

[Ursa (9R)]

I think it's clearer to just look these up by key.

[Multipartite]

Here I'd like to hear from @pluto-9r who originally chose the number format in case having a significant preference for it
( https://gitlab.com/thorchain/thornode/-/blame/80a23f9f/test/regression/suites/mimir/mimir_v2.yaml#L95-106 )
; the [0]/[1] format is significant for this MR in reflecting the deterministic order,
but if you were to both acknowledge
{the MR's implemented deterministic order} and {that not needing (future) regtest reflection of this}
I would be happy to add another commit to switch to the ."1-GLOBAL".id format instead.