Align subnet VM versions list with compatible AvalancheGo versions #2868
Description
Currently when a new version of a VM (say SubnetEVM) is released, it immediately becomes available on the CLI. However when a new version of AvalancheGo the CLI doesn't seem to know about it. Because of this, trying to use the CLI with the default setting to create and deploy L1s might fail if there's a too recent VM version that uses a different RPC version.
For example right now, with the latest version of the CLI, the latest version available for Avalanche is 1.13.2 with RPC version 41. The latest SubnetEVM is 0.7.5 with RPC version 41. The CLI knows about SubnetEVM 0.7.5 but avalanche network start will download avalanchego 1.13.1 which has RPC version 40, so it will be impossible to deploy a newly created l1 with default settings.
Ideally, the CLI should know to download the latest release of AvalancheGo but ff for some reason it is desired for the CLI to not do that, then I suggest we update the default behaviour when creating an L1 to make it use the latest available Subnet that would be deployable on the avalanchego version that is supported by the CLI.