feat: improve Seedance discovery and illustrated onboarding

[acedatacloud-dev]

Make Seedance discoverable as an independent Cursor integration with clear Ace Data Cloud identity, and complete the illustrated token-to-first-use guide before official review.

• Display name Seedance by Ace Data Cloud, relevant deduplicated service/capability keywords and version 1.0.1. Preserve stable slug, Ace author and logo; no brand-official or live-marketplace claim.
• English/Chinese installation -> registration/login -> Applications/General application -> copy/create dedicated API token -> Cursor Configure -> first use -> same-ID task retrieval/result -> billing/FAQ. Registration, token and price CTAs retain the existing four-field opensource/referral/evergreen convention for a shared README.
• Include masked real Ace console screenshots with exact source/date/checksums, unedited official Cursor tool UI references, and (Suno only) an explicitly marked official-original screenshot edit preview. Do not substitute these for a native Configure screenshot or claim actual execution. The historical Dify key-name example is explained as replaceable with a Cursor-specific name.
• Hosted MCP JSON, variable/auth behavior, Skills, examples, model parameters, fallback and prices are unchanged. Source and existing official candidate contents match byte for byte.

Validation: current official plugin validator and generated-harness check pass on the latest official-base candidate; Markdown local image/link checks and git diff --check pass. Images visually checked for hidden credentials. No paid generation, deployment or merge. Official listing/search/normal install remain pending at cursor/plugins#549; no ranking/install/revenue claims. Adversarial review not requested.