Add Zircuit Layer 2 network

[konopkja]

Summary

Adds Zircuit as a new Layer 2 network to ethereum.org.

Changes:

• Added Zircuit logo to /public/images/layer-2/
• Added Zircuit entry to layer2Data in networks.ts
• Added Zircuit ID to growthepieIds.ts
• Added description translation to page-layer-2.json

About Zircuit:

Zircuit is an EVM-compatible ZK Rollup built on the OP Stack architecture with zkVM provers. It features AI-powered Sequencer-Level Security (SLS) that detects and prevents malicious transactions before they reach the blockchain.

• Type: ZK Rollup
• Website: https://zircuit.com
• L2BEAT: https://l2beat.com/scaling/projects/zircuit
• Explorer: https://explorer.zircuit.com
• Live since: July 2, 2024

Closes #16837

Test plan

• Verify Zircuit appears on the Layer 2 page
• Verify all links work correctly
• Verify logo displays properly

🤖 Generated with Claude Code

[netlify]

✅ Deploy Preview for ethereumorg ready!

Name	Link
🔨 Latest commit	96b36b9
🔍 Latest deploy log	https://app.netlify.com/projects/ethereumorg/deploys/6960273e2a50100008acc132
😎 Deploy Preview	https://deploy-preview-17036.ethereum.it
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	7 paths audited Performance: 55 (🟢 up 3 from production) Accessibility: 94 (no change from production) Best Practices: 100 (🟢 up 1 from production) SEO: 100 (no change from production) PWA: 59 (no change from production) View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[minimalsm]

The Zircuit integration looks comprehensive! A few observations on the mock data files:

1. fetch-grow-the-pie.json - The value 0.00012345678901234567 looks like a placeholder rather than realistic test data. Consider using a more realistic mock value.

2. fetch-l2beat.json - The TVL of 350000000 and fetch-grow-the-pie.json active addresses of 45000 - are these based on actual Zircuit metrics, or placeholders? For mock data consistency, it might help to use values closer to L2BEAT's real data.

3. Good catch on networkMaturity.ts - The null checks you added (if (!l2beatData?.risks) and if (!l2beatData)) are solid defensive improvements.

4. Minor - The description says "EVM-compatible ZK Rollup" but L2BEAT shows Zircuit as being built on OP Stack architecture with zkVM provers (a hybrid approach). The current description is accurate for end-users, just noting for awareness.

Overall the structure follows the existing patterns well.