Restructure DuskVM contract documentation

[HDauven]

Summary

• replace the stale single-page DuskVM contract guide with concise overview, quickstart, and reference pages
• document the Forge v0.3 workflow from installation through testnet deployment and calls
• position Dusk Connect as the wallet-extension integration layer for Dusk browser dApps
• replace the stale raw wallet-provider example with the released @dusk/connect profile flow
• normalize the architecture vocabulary across the docs: Dusk for the product/network umbrella, Dusk L1 for the complete base layer, DuskDS for settlement and data availability, DuskVM for direct Rust/WASM execution, and DuskEVM for EVM execution
• use DuskVM versus DuskEVM as the developer-facing choice instead of Native Dusk versus DuskEVM
• move the developer pages from /developer/duskds/* to /developer/duskvm/*, retaining permanent redirects for existing links
• distinguish Dusk L1 terminology from the current bridge UI's visible DuskDS label
• update navigation, internal links, the glossary, architecture pages, and static LLM indexes
• add the missing W3sper custom-contract/data-driver handoff and correct the wallet-core driver version

Correctness validation

• installed Forge v0.3.0 into a clean Cargo home and ran a clean scaffold, check, test, build, schema, call encoding, and verify workflow
• deployed the generated counter to a fresh local Rusk 1.7.1 state and verified state transitions from 0 to 1 to 42
• loaded the generated data-driver WASM through W3sper and verified its schema and decoded get_count result
• checked commands and behavioral claims against clean Forge v0.3.0 and Rusk 1.7.0 source trees
• verified the @dusk/connect 0.2.0 GitHub release, published JSR exports, and canonical wallet provider API
• checked the bridge terminology against the current Web Wallet interface
• completed an independent source-backed factual review and resolved all findings
• verified the current mainnet and testnet wallet-core 1.6.1 WASM endpoints

Site checks

• npm run build
• git diff --check
• all internal links valid
• canonical DuskVM routes return 200
• retired DuskDS developer routes permanently redirect to their DuskVM equivalents