Improve network versioning

[HDauven]

Summary

Currently the node installer relies on the Rusk and Rusk wallet binaries provided by the installer itself. There is logic to retrieve the latest release from the Rusk repository, but both approaches are problematic when Devnet, Testnet and Mainnet run on different Rusk versions. This will at some point cause version management issues, as Devnet will always be ahead of Testnet and Mainnet.

Possible solution design or implementation

To prevent any issues, we should introduce versioning within the network configuration function. The installer should pull the correct Rusk version for the given network instance.

Preferably we stick to the current installer structure to minimize maintenance overhead, reduce the chance of breaking a network or having broken links in our docs.