Add HyperSDK Functionality to CLI

[RodrigoVillar]

Why this should be merged

With the HyperSDK maturing, we would like to make it a first-class citizen (i.e. the same level of support as Subnet-EVM). By doing this, HyperSDK developers benefit from the following:

• Fast Deployments: by being able to use the Avalanche-CLI, developers no longer have to start up their VM via integration/e2e tests
• Learning: using the Avalanche-CLI is a lower barrier-of-entry for potential HyperSDK developers than the current test framework

How this works

This PR separates HyperVMs (VMs built with HyperSDK) from the custom VM group and makes it a group of its own. Therefore, we now have three types of VMs in the CLI:

• SubnetEVM
• HyperVMs
• Custom VMs

The biggest change is in the avalanche blockchain create command, where users are now able to select the option of creating a HyperVM. When selecting this option, the control flow is similar to that of Subnet-EVM, with the exception of the genesis.

In addition to being able to provide a genesis.json file and being able to use the default HyperSDK genesis, users can also use their VM binary to create the VM genesis on their behalf.

How this was tested

How is this documented

We plan on adding documentation for this feature in the HyperSDK docs.

cc: @felipemadero @aaronbuchwald