fix: lock binaries version (#752)

Description
---
fixes: #731 
Lock binaries version excatly as listed in
`binaries_versions_nextnet.json` and `binaries_versions_esmeralda.json`

Motivation and Context
---
If not specified tari univese V1 could use newer version of binaries.

How Has This Been Tested?
---
Check installed binaries (in my case
`~/.cache/com.tari.universe.alpha/binaries` and chaged to some lower
version in `binaries_versions_esmeralda.json` and check if there are new
installed binaries.

What process can a PR reviewer use to test or verify this change?
---
Same as above.

Breaking Changes
---

- [x] None
- [ ] Requires data directory on base node to be deleted
- [ ] Requires hard fork
- [ ] Other - Please specify

Co-authored-by: stringhandler <[email protected]>

src-tauri/binaries_versions_esmeralda.json

@@ -1,11 +1,11 @@
 {
     "binaries": {
-        "xmrig": "6.22.0",
-        "mmproxy": "1.6.0-pre.0",
-        "minotari_node": "1.6.0-pre.0",
-        "wallet": "1.6.0-pre.0",
-        "sha-p2pool": "0.1.9",
-        "xtrgpuminer": "0.1.10",
-        "tor": "13.5.6"
+        "xmrig": "=6.22.0",
+        "mmproxy": "=1.6.0-pre.0",
+        "minotari_node": "=1.6.0-pre.0",
+        "wallet": "=1.6.0-pre.0",
+        "sha-p2pool": "=0.1.9",
+        "xtrgpuminer": "=0.1.10",
+        "tor": "=13.5.6"
     }
-}
+}

src-tauri/binaries_versions_nextnet.json

@@ -1,11 +1,11 @@
 {
     "binaries": {
-        "xmrig": "6.22.0",
-        "mmproxy": "1.5.1-rc.3",
-        "minotari_node": "1.5.1-rc.3",
-        "wallet": "1.5.1-rc.3",
-        "sha-p2pool": "0.1.9",
-        "xtrgpuminer": "0.1.10",
-        "tor": "13.5.6"
+        "xmrig": "=6.22.0",
+        "mmproxy": "=1.5.1-rc.3",
+        "minotari_node": "=1.5.1-rc.3",
+        "wallet": "=1.5.1-rc.3",
+        "sha-p2pool": "=0.1.9",
+        "xtrgpuminer": "=0.1.10",
+        "tor": "=13.5.6"
     }
-}
+}