Add CRYMAD Chain (1475) and CRYMAD Chain L2 (7373)

[myfxpaddy]

Adds CRYMAD Chain (1475) and CRYMAD Chain L2 (7373). Both run self hosted Blockscout.

	1475	7373
Explorer	https://explorer.cmxofficial.com	https://explorer-l2.cmxofficial.com
Layer	1	2, optimistic, settles to 1475
Native currency	CMX-R	CMX-R
Average block time	0.66s	0.15s

Both explorers are live and serving the v2 API:

$ curl -s https://explorer.cmxofficial.com/api/v2/stats     | head -c 60
$ curl -s https://explorer-l2.cmxofficial.com/api/v2/stats  | head -c 60

Both chains were merged into ethereum-lists/chains today
(ethereum-lists/chains#8766), so the chain IDs, names and native currency here
match the canonical registry entries.

Only the two new entries are added. Every one of the 712 existing entries is byte
identical, and the file still parses as valid JSON with 714 entries.

[NikitaSavik]

First explorer is not Blockscout frontend and has not Blockscout attribution
Second explorer doesn't work and misconfigured.

[myfxpaddy]

Thank you, both points were correct and both are now fixed.

Second explorer, explorer-l2.cmxofficial.com. You were right, and the cause was worse than it
looked. Its common-frontend.env was still carrying the stock example values, so
NEXT_PUBLIC_API_HOST and NEXT_PUBLIC_APP_HOST were literally localhost, with
STATS_API_HOST and VISUALIZE_API_HOST on localhost:8080 and localhost:8081. Every visitor's
browser was being told to fetch chain data from its own machine, which is exactly the behaviour you
flagged. Only the network identity had been overridden when it was set up.

It now serves the real host over https and wss, and stats and visualizer are proxied same origin so
nothing reaches out to a visitor's machine:

$ curl -s https://explorer-l2.cmxofficial.com/assets/envs.js | grep -c localhost
0

First explorer, explorer.cmxofficial.com. Attribution added, linking to blockscout.com in the
footer on every page, per clause 2(c) of the licence. That was our oversight and we are sorry for it.

On your other point there, you are also right that it is not the Blockscout frontend. It is a
Blockscout backend with a custom UI in front of it. Before I open anything else, would you rather
we list only the L2, which runs the stock Blockscout frontend, or is a Blockscout backed instance
with its own frontend and correct attribution acceptable for Chainscout? Happy to follow whichever
you prefer.