cli warp deploy should prompt for native metadata

[ltyu]

Problem

Currently, using hyperlane warp deploy to deploy a native token expects the nativeToken property either in the metadata.yaml (registry) or the warpConfig. If this is not provided, the CLI will panic. To get around this is, users must manually add nativeToken into the metadata file. This is problematic because CLI users are not aware of this issue, and may not know how to respond.

Solution

• Consider adding prompts for this if it is missing from the metadata
• If there is no preference, it is easier to keep nativeToken inside of metadata.ts as there are many dependencies on this such as (igp.ts, gas-oracle.ts, etc.)
• Subsequently, update the metadata or warp config with the user entered values