story: Split wallet docs into an end-user page and a developer wallet-integration page

Part of #2266.

### User story

As a reader, I want to know from the first sentence whether a wallet page is for me as someone who holds CELO, or for me as someone integrating wallets into an app — so I stop landing on the wrong list.

### Context & evidence

At `bdf40b37` there are two wallet pages with different audiences and overlapping content:

- `home/wallets.mdx` — end-user list of compatible wallets
- `tooling/wallets/index.mdx` — `## Celo Native Wallets` (MiniPay, Valora, Celo Terminal) **plus** `## Wallet Infrastructure` (line 58) listing 11 developer providers: Privy, Openfort, Alchemy Smart Wallets, thirdweb, Reown, BlockRadar, Para, Safe, Zerion, Portal, JAW

The native-wallet list is duplicated; the rest diverges. `tooling/wallets/{metamask,ledger}/*` are end-user setup guides living in the developer tab. Wallet content has been moved, split and merged repeatedly; decided: make the audience explicit per page, once.

### Acceptance criteria

- [ ] One **end-user** page: native + compatible wallets, links to the MetaMask / Ledger setup guides; the first paragraph says it is for people holding CELO
- [ ] One **developer** "Wallet integration" page holding the 11 providers as a neutral list (thirdweb stays as a plain entry — #2255)
- [ ] The native-wallet list exists exactly once; the other page links to it
- [ ] Titles and sidebar titles state the audience (e.g. "Wallets for users" / "Wallet integration"; OPEN: exact wording)
- [ ] Done **in place** — no directory moves (#2258 / #2259 move the files)
- [ ] `npx mintlify broken-links` green

### Non-goals

Listing these wallets on the ecosystem site (#2265); the MetaMask image bug #2156 (link, don't fix here).

### Depends on / blocks

Depends on #2253 (decides the orphaned `tooling/wallets/coinbase-wallet.mdx` and `tooling/wallets/ledger/eip712-workaround.mdx`). Blocks #2258, #2259.

**Measured at:** `bdf40b37`