Request: Display official KriptoAman Mainnet icon (Chain ID 22028)

## What is this about?

Request MetaMask Mobile to display the official network icon for **KriptoAman Mainnet** (Chain ID **22028 / 0x560c**) instead of a generic/default icon when the network is added and shown in MetaMask Mobile.

KriptoAman Mainnet metadata and icon are already merged into the public `ethereum-lists/chains` registry.

## Scenario

- GIVEN a user adds or selects KriptoAman Mainnet in MetaMask Mobile
- WHEN MetaMask Mobile displays the network in the network selector or other network UI
- THEN MetaMask Mobile should display the registered KriptoAman network icon associated with Chain ID 22028

## Design

Use the already registered network icon from `ethereum-lists/chains`:

- Icon slug: `kriptoaman`
- IPFS: `ipfs://bafkreicorcwbkyjyw3rdbvuxfpw7bvrf74nsp4vaakclaoh6a67enzd36a`
- Format: PNG
- Dimensions: 512 × 512

## Technical Details

- Network name: KriptoAman Mainnet
- Chain ID: `22028` (`0x560c`)
- Network ID: `22028`
- Native currency: KAM, 18 decimals
- RPC: https://rpc.kriptoaman.com
- Explorer: https://explorer.kriptoaman.com
- Website: https://kriptoaman.com
- Documentation: https://kriptoaman.com/KAMNetworkDocs
- ethereum-lists metadata: https://github.com/ethereum-lists/chains/blob/master/_data/chains/eip155-22028.json
- icon metadata: https://github.com/ethereum-lists/chains/blob/master/_data/icons/kriptoaman.json
- merged registry PR: https://github.com/ethereum-lists/chains/pull/8639

The registry entry contains `"icon": "kriptoaman"`, `"chainId": 22028`, and `"networkId": 22028`.

The public RPC is live and returns `eth_chainId = 0x560c`. The explorer is publicly reachable and the network is actively producing blocks.

## Threat Modeling Framework

- What are we working on? Displaying the correct official icon for an already registered EVM network.
- What can go wrong? A generic or incorrect icon could confuse users about which network is selected.
- What are we going to do about it? Use the canonical icon mapping already registered for Chain ID 22028.
- Did we do a good job? Success means the correct KriptoAman icon is consistently displayed wherever MetaMask Mobile renders the network identity.

## Acceptance Criteria

- [ ] MetaMask Mobile recognizes Chain ID 22028 as KriptoAman Mainnet when added as a custom EVM network.
- [ ] The official `kriptoaman` icon is displayed in the network selector and relevant network UI.
- [ ] The icon source maps to the canonical registry metadata already merged in `ethereum-lists/chains`.
- [ ] Existing RPC/explorer behavior remains unchanged.

## Stakeholder review needed before the work gets merged

- [ ] Engineering (needed in most cases)
- [ ] Design
- [ ] Product
- [ ] QA
- [ ] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management
- [ ] Other

## References

- ethereum-lists PR #8639: https://github.com/ethereum-lists/chains/pull/8639
- Chain metadata: https://github.com/ethereum-lists/chains/blob/master/_data/chains/eip155-22028.json
- Icon metadata: https://github.com/ethereum-lists/chains/blob/master/_data/icons/kriptoaman.json
- MetaMask Extension issue #45821: https://github.com/MetaMask/metamask-extension/issues/45821
- DefiLlama Chainlist PR #3089: https://github.com/DefiLlama/chainlist/pull/3089
- Official website: https://kriptoaman.com

Start at MetaMask Mobile's network selector and network identity rendering, then trace how chain metadata and icons are resolved for custom EVM networks. Compare the behavior with the ethereum-lists chain and icon metadata for Chain ID 22028. Done means the registered KriptoAman icon appears consistently in the relevant network UI without changing RPC or explorer behavior.

Written by the indexing model from the issue text.