fix: clarify precompile address allocation

[daixihegu]

Fixes #417.

The precompiled contracts introduction said that addresses start from 1 and increment for each contract. That is true for the early precompiles, but no longer accurate for the full table now that newer hardforks include non-contiguous addresses such as 0x100 for P256VERIFY.

This updates the wording to say that early precompiles use sequential addresses starting from 1, while newer hardforks may introduce precompiles at non-contiguous addresses.

I have verify this change by executing:

• pnpm exec prettier --check pages/precompiled.tsx
• pnpm exec eslint --ext js,jsx,ts,tsx pages/precompiled.tsx
• pnpm typecheck

[vercel]

@daixihegu is attempting to deploy a commit to the Duneanalytics Team on Vercel.

A member of the Team first needs to authorize it.

[cursor]

PR Summary

Low Risk
Copy-only change on a docs page; no runtime, gas, or routing logic is affected.

Overview
Updates the Precompiled Contracts introduction on pages/precompiled.tsx so it no longer claims every precompile gets the next address after 1.

The text now states that early precompiles use sequential addresses from 1, while later hardforks may add precompiles at non-contiguous addresses (e.g. 0x100 for P256VERIFY). Wording around CALL, gas cost, and the playground is unchanged aside from line wrapping.

^{Reviewed by Cursor Bugbot for commit 08a0712. Configure here.}