[Bug]: ACP-77 Deploy Flow Bugs

[owenwahlgren]

Describe the bug

• The error code should be different when avalanche blockchain deploy is finished
• The describe command no longer works after deployment

Note This is on ACP-77 branch

To Reproduce
Create chain:

./avalanche blockchain create myblockchain --force

✔ Subnet-EVM
✔ Proof Of Authority
✔ Get address from an existing stored key (created from avalanche key create or avalanche key import)
✔ ewoq
✓ Validator Manager Contract owner address 0x8db97C7cEcE249c2b98bDC0226Cc4C2A57BF52FC
Chain ID: 1001
✔ Chain ID: 1001█
Token Symbol: OWEN
prefunding address 0x8db97C7cEcE249c2b98bDC0226Cc4C2A57BF52FC with balance 1000000000000000000000000
✓ Successfully created blockchain configuration

Deploy chain:

./avalanche blockchain deploy myblockchain

Devnet Endpoint: https://etna.avax-dev.network✔
How many bootstrap validators do you want to set up?: 1
If you have set up your own Avalanche Nodes, you can provide the Node ID and BLS Key from those nodes in the next step.
Otherwise, we will generate new Node IDs and BLS Key for you.
✔ No
Getting info for bootstrap validator 1
✔ Get address from an existing stored key (created from avalanche key create or avalanche key import)
✔ ewoq
✓ Bootstrap Validator 1:
- Node ID: NodeID-BVvKo7RSKu2CpPXdra8RdFsWcChA8N1ry
- Change Address: P-custom18jma8ppw3nhx5r4ap8clazz0dps7rv5u9xde7p
Deploying [myblockchain] to Devnet https://etna.avax-dev.network
✔ Use stored key
✔ ewoq
Your Subnet's control keys: [P-custom18jma8ppw3nhx5r4ap8clazz0dps7rv5u9xde7p]
Your subnet auth keys for chain creation: [P-custom18jma8ppw3nhx5r4ap8clazz0dps7rv5u9xde7p]
CreateSubnetTx fee: 0.000000686 AVAX
Subnet has been created with ID: E8TcWXN6wyBU9hTrFZbBMwKovBt3fbjmgURbAjnyZ1tinGZjz
Now creating blockchain...
CreateChainTx fee: 0.000114564 AVAX
+--------------------+----------------------------------------------------+
| DEPLOYMENT RESULTS |                                                    |
+--------------------+----------------------------------------------------+
| Chain Name         | myblockchain                                       |
+--------------------+----------------------------------------------------+
| Subnet ID          | E8TcWXN6wyBU9hTrFZbBMwKovBt3fbjmgURbAjnyZ1tinGZjz  |
+--------------------+----------------------------------------------------+
| VM ID              | qDNV9vtxZYYNqm7TN1mYBuaaknLdefDbFK8bFmMLTJQJKaWjV  |
+--------------------+----------------------------------------------------+
| Blockchain ID      | 2jMBpU7C2UGLoDX9qx2886SELnfR8GMFFbbZX5Q1mitZ7Gagcd |
+--------------------+                                                    +
| P-Chain TXID       |                                                    |
+--------------------+----------------------------------------------------+
Now calling ConvertL1 Tx...
ConvertSubnetTX fee: 0.000001414 AVAX
ConvertL1Tx ID: 2pyDNfiUXRVqJLSDFASM3d6ddJdwxXFXxrC5Ed3vqy8ScKpnSW
Waiting for Blockchain to be converted into Subnet Only Validator (SOV) Blockchain ... 100% [===============]           
Error: no Avalanche nodes found that can track the blockchain, please create Avalanche nodes first through `avalanche node create`

Attempt to describe chain:

./avalanche blockchain describe myblockchain

Error: unsupported network name

Expected behavior
Since the p-chain transactions are all successful, the error message should tell the user "Success" and either start a new node using --track-subnets with the newly made SubnetID or the node should be spun up automatically with the generated Node IDs and BLS Key.

The describe command should also print out network information.

Operating System
Mac OSX