"EVM Version" missing after verifying EVM contract with hardhat

Nobody has claimed this yet.

#### 📝 Description

When using the etherscan plugin with Hardhat to verify an EVM contract, verification works, but the "EVM Version" is missing from the explorer

#### 🔄 Reproduction Steps

1. Create a hardhat project with `npx hardhat init`.
2. Deploy the contract to Era Sepolia testnet.
3. Add etherscan object to hardhat config with EVM verification endpoints:
```ts
etherscan: {
apiKey: {
// no API key is required
ZKsyncEraSepolia: "",
ZKsyncEraMainnet: "",
},
customChains: [
{
network: "ZKsyncEraSepolia",
chainId: 300,
urls: {
apiURL: "https://block-explorer-api.sepolia.zksync.dev/api",
browserURL: "https://sepolia.explorer.zksync.io"
}
},
{
network: "ZKsyncEraMainnet",
chainId: 324,
urls: {
apiURL: "https://block-explorer-api.mainnet.zksync.io/api",
browserURL: "https://explorer.zksync.io"
}
}
]
},
```
4. Run `npx hardhat verify --network mainnet DEPLOYED_CONTRACT_ADDRESS "Constructor argument 1"`.
5. See on the explorer that the contract was verified, but the "EVM Version" is missing:

#### 🤔 Expected Behavior

The explorer should display the EVM version automatically.

#### 😯 Current Behavior

It's missing.

Reproduce the missing EVM version using the Hardhat verification steps and the ZKsync Era Sepolia or Mainnet explorer endpoints shown in the issue. Trace the verification request through the explorer and compare the returned contract metadata with what the contract page displays; done means a verified contract shows its EVM version.

Written by the indexing model from the issue text.