Default domainId and protocolType (#3041)

### Description

We only support EVM chains today, so folks pretty much should always use the chainId as the domainId and not choose any other protocol type other than ethereum. So removing the optionality for now until that changes

.changeset/purple-bulldogs-report.md

@@ -0,0 +1,5 @@
+---
+'@hyperlane-xyz/cli': patch
+---
+
+Remove domainId and protocolType setting when creating chain config

typescript/cli/src/config/chain.ts

@@ -1,4 +1,4 @@
-import { confirm, input, select } from '@inquirer/prompts';
+import { input } from '@inquirer/prompts';
 
 import {
   ChainMap,
@@ -81,30 +81,13 @@ export async function createChainConfig({
     message: 'Enter chain name (one word, lower case)',
   });
   const chainId = await input({ message: 'Enter chain id (number)' });
-  const skipDomain = await confirm({
-    message: 'Will the domainId match the chainId (recommended)?',
-  });
-  let domainId: string;
-  if (skipDomain) {
-    domainId = chainId;
-  } else {
-    domainId = await input({
-      message: 'Enter domain id (number, often matches chainId)',
-    });
-  }
-  const protocol = await select({
-    message: 'Select protocol type',
-    choices: Object.values(ProtocolType).map((protocol) => ({
-      name: protocol,
-      value: protocol,
-    })),
-  });
+  const domainId = chainId;
   const rpcUrl = await input({ message: 'Enter http or https rpc url' });
   const metadata: ChainMetadata = {
     name,
     chainId: parseInt(chainId, 10),
     domainId: parseInt(domainId, 10),
-    protocol,
+    protocol: ProtocolType.Ethereum,
     rpcUrls: [{ http: rpcUrl }],
   };
   const parseResult = ChainMetadataSchema.safeParse(metadata);