use the chain name as a blockchain alias

[boulix3]

Related to the issue #476
I chose to use the subnet name as the blockchain alias. I figured it was not useful to ask for another parameter since there can only have one chain per subnet with avalanche-cli.

[boulix3]

Here is an example with a subnet-evm.
You can make the same query with the alias or the blockchainId in the rpc url.

$ curl -X POST --data '{
    "jsonrpc":"2.0",
    "id"     :1,
    "method" :"eth_baseFee",
    "params" :[]
}' -H 'content-type:application/json;' http://127.0.0.1:9650/ext/bc/mysubnet/rpc
{"jsonrpc":"2.0","id":1,"result":"0x5d21dba00"}
$ curl -X POST --data '{
    "jsonrpc":"2.0",
    "id"     :1,
    "method" :"eth_baseFee",
    "params" :[]
}' -H 'content-type:application/json;' http://127.0.0.1:9650/ext/bc/2VqqvGNY71aVWm1V29HvNiv6TrdHvpg3kvceKVYP2PVrcVUe6A/rpc
{"jsonrpc":"2.0","id":1,"result":"0x5d21dba00"}

[boulix3]

Here is a screenshot of the subnet creation wizard output where we can see the ALIASURL column.

[boulix3]

@dasconnor can you please check this out?

[dasconnor]

If you fix the failing tests, we can merge this

[boulix3]

If you fix the failing tests, we can merge this

It's fixed.

[dasconnor]

LGTM Thanks for the patience!

[dasconnor]

Sorry, one last ask, can you sign your commit? https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits

[boulix3]

Sorry, one last ask, can you sign your commit? https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits

No problem, I just squashed my old commits and signed the new commit.

[dasconnor]

All merged! It'll go out in the next release, probably later this week.