Migrate existing `core` / `chain` CLI config management to new setup

[tkporter]

Note that atm, config management in the CLI's "core config" is a mix of the chain config, ism config (migration tracked here https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3536), and hook config (migration tracked here https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3534).

• [ ] Move hyperlane config create chain to hyperlane core config create-chain
  • (feel free to come up with a better name)
• [ ] Move hyperlane config validate chain to hyperlane core config validate-chain
  • (feel free to come up with a better name)
• [ ] Create a new command, hyperlane core config output
  • (feel free to come up with a better name)
  • This should be the new home of existing logic in the CLI that reads in the concise CLI-specific chain configs relating to the CLI-generated ISM / hook / chain configs (the ones used by the create or validate commands) and outputs a "verbose config" that is a ChainMap<CoreConfig> to stdout

[yorhodes]

• owner should default to HYP_KEY address following https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3724