Improve Structure + Fix Broken Links in TypeScript WebClient Docs

While reviewing the Miden client documentation, I noticed that the TypeScript WebClient section needs improvement in two key areas:

1. Structural Consistency with Rust Docs
The Rust section has a well-organized hierarchy:

- Installation

- Getting Started

- Features

- Examples

- CLI, etc.

In contrast, the TypeScript docs are flat and lack clear onboarding sections like:

- Setup / Installation

- Getting Started

- Usage Examples

Suggestion:
Adopt a similar structure as Rust for TypeScript WebClient to improve navigation and developer onboarding.

2. Broken Links in TypeScript (WebClient) Documentation
Several internal links are currently broken in the TypeScript WebClient documentation, making it difficult to navigate or reference key types and modules

Examples:

In the Accounts section
- Broken internal links to:
- Webclient
- Account
- AccountID

Other sections like import, export, sync, transactions, etc. also have broken internal references.

Would be good to audit and fix these across the WebClient docs

Start by locating the TypeScript WebClient documentation files in the repository, likely in a docs/ or similar directory. Audit the internal links mentioned (Accounts, Webclient, Account, AccountID, import, export, sync, transactions) to identify broken references. Then, restructure the documentation to mirror the Rust section's hierarchy (Installation, Getting Started, Features, Examples). Verify fixes by building or previewing the docs locally.

由索引模型根据 Issue 内容生成。