Update the information architecture

The following suggestion comes from the PaperMoon:

Learn
- What is Darwinia?
- Architecture
- EVM Compatibility
  - Overview
  - AccountSystem
  - Gas
- Staking
- Governance
- FAQ
Build
- Get Started
  - Networks
    - Overview
    - Darwinia
    - Crab
    - Pangolin
    - Rollup Testnet
    - Development Node
      - Run a Development Node
      - Development Accounts
  - RPC Endpoints
  - Block Explorers
  - Testnet Faucet
  - Wallets
- Development Tools
  - Ethereum Tools
    - Web3 Libraries
      - Ethers
      - Web3
    - Development Environments
      - Hardhat
      - Foundry
    - Verify Contracts
  - Substrate Tools
    - Polkadot.js API
  - Protocol Integrations
    - Indexers
      - SubQuery
- Precompiled Contracts
  - Overview
  - Asset
    - KTON
    - USDT
  - Governance
  - Conviction Voting
  - Staking
    - Staking
    - Deposit
  - Utility
    - Ethereum Mainnet
    - Dispatch
    - StateStorage
Network Operators
- Get Started
- Database Snapshots
- Run an Archive Node
- Run an Collator Node
- Run an Tracing Node
Community
- Overview
- Community Organizations
  - RingDAO
  - DCDAO
  - KtonDAO
- Community Guide
  - Accounts
    - How to Create an Account
    - How to Create a Multisig
    - Account Migrations from Darwinia 1.0
      - How to migrate Existing Accounts
      - How to migrate Existing Multisigs
  - Token Transfers
    - How to Transfer Native Token
    - How to Transfer USDT
  - Staking
    - How to stake
  - Governance
    - How to submit a Governance Proposal
    - How to Vote on a Proposal
    - How to Create a DAO

Overall, the structure is okay for me, but I also have some opinions:

Some subsections are nested too deep, such as Run a Development Node and Development Accounts, I prefer to keep them in one section Development Node.
Community, Community Organizations and Community Guide are renamed to User, User Organizations and User Guide

darwinia-network / docs

Update the information architecture #49