docs(services): update Infura introduction with MetaMask context and architecture overview

[rohan911438]

Description

Fixes #1387

This PR updates the Services introduction to better explain the relationship between MetaMask and Infura, providing additional context for developers using Infura as an RPC provider.

Changes

• Reworked the introductory content to be more MetaMask-focused.

• Added clarification on the distinct responsibilities of MetaMask and Infura.

• Explained the transaction lifecycle, including:

  • Transaction signing in MetaMask.
  • Transaction broadcasting through Infura endpoints.

• Added guidance on accessing blockchain data through Infura.

• Added context around network switching and endpoint selection.

• Added a simplified architecture diagram illustrating:

  • User interaction flow.
  • MetaMask transaction signing.
  • Infura RPC endpoint communication.
  • Blockchain network access.

Why

The previous introduction primarily described Infura services but did not clearly explain how those services fit into a typical MetaMask developer workflow.

These updates provide a clearer mental model for developers by explaining:

• How MetaMask and Infura work together.
• The difference between signing and broadcasting transactions.
• How Infura provides scalable blockchain data access.
• How developers can use Infura endpoints across supported networks.

Files Updated

• services/index.md
• developer-tools/dashboard/index.mdx (if applicable)

Testing

• Verified documentation builds successfully.
• Verified internal links and navigation.
• Reviewed content for consistency with existing Services documentation style.

---

Note

Low Risk
Documentation-only edits with no runtime, auth, or data-path changes.

Overview
Services introduction is reframed around MetaMask + Infura: wallet signing and key custody vs hosted JSON-RPC/REST for reads and broadcasting, plus what these docs cover (local signing, provider broadcast, endpoint choice).

A new How it works section adds a Mermaid flow (user → MetaMask → local sign → Infura → chain), narrative on eth_sendRawTransaction and read methods, an important admonition on signing vs broadcasting and never sharing keys, and network switching guidance (chainId and matching Infura endpoints).

Infura dashboard intro gains one sentence clarifying that API keys are created in Infura and that MetaMask documents usage but does not manage Infura accounts or keys.

^{Reviewed by Cursor Bugbot for commit 71e3aee. Bugbot is set up for automated code reviews on this repo. Configure here.}

[vercel]

@rohan911438 is attempting to deploy a commit to the Consensys Team on Vercel.

A member of the Team first needs to authorize it.